The install is one line: npm install -g @snap/easylens-cli@latest. What arrives is the Easy Lens CLI, Snap's new command line tool for making Snapchat Lenses, and the package metadata on the npm registry states the job plainly: "Build, inspect, and publish Snapchat lenses from the command line."
Snap's Easy Lens CLI Puts a Lens Build on npm, With Native Binaries for Only Three Platforms
A Lens is the AR effect you wear on your face in Snapchat, the thing most people still call a filter. You used to build one in Lens Studio, Snap's desktop editor, or in Easy Lens, the prompt driven web and phone tool that generates a Lens from a sentence. The CLI is a third door, aimed at whatever coding agent you already keep open.
Snap's page for it, at easylens.snapchat.com/cli, leads with "Bring your AI. Build a Lens" and a picker holding four options: Claude Code, Cursor, Codex CLI, and "Any other agent". Pick one and the page hands you text to paste into that agent. It tells the agent to run the install, have it print the installed version, then run easylens agent print and follow the guide bundled inside the binary. Named agents also get easylens agent init with a target of claude, cursor or codex, which writes project instructions where that tool looks for them and is told to preserve anything already there. Sign-in is easylens auth login.

None of this is Snap's first move toward agents. CLAD, documented at docs.lensstudio.com, already runs an MCP server that lets Claude Code, Cursor, VS Code or Codex drive Lens Studio directly, with a setup page per tool. The CLI is a separate install, and as of today it has no page in those docs at all.
What actually installs
Open the npm package and there is almost nothing inside. Four files. The one that runs, bin/easylens.js, is roughly a kilobyte of Node that builds no Lens and calls no Snap API. It reads your platform and architecture, resolves @snap/easylens-cli-<platform>-<arch>, and hands your arguments to a compiled executable inside it. Its own comment says the real binary "lives in the platform package that npm's optionalDependencies resolution installed for this OS/arch."
Three of those platform packages exist. Unpacked, the macOS Apple Silicon build runs about 75 MB across 36 files, the x64 Linux build about 103 MB, the x64 Windows build about 70 MB. The npm part is a launcher and a download. The tool is a native program that happens to arrive through a JavaScript package manager.
Check your hardware before you paste that prompt. No darwin-x64 package exists, so an Intel Mac gets nothing. Neither linux-arm64 nor win32-arm64 exists either, which rules out Snapdragon Windows laptops and ARM Linux boxes. The shim at least fails politely, printing the architecture it looked for and the package it could not find before it exits.
The version history dates this launch better than any press cycle will. The package appeared on npm on November 6 as 0.0.0-stage, with three smoke test builds in the same half hour. The first real version, 0.2.83, went up on November 13, then 0.2.88 and 0.2.97 on November 16 and 0.2.99 on November 17. Four days of real releases, and the number still starts with a zero. Node 18 or newer.

Free to install is not free to read
The package license field reads "SEE LICENSE IN README.md", and the README sends you to Snap's Lens Studio License Agreement, with anything generative governed separately by Snap's Generative Lens Tools Terms. There is no repository link, no source, and a third party notices file covering the libraries Snap compiled in. You can install this tool in ten seconds and you cannot read a line of it.
That is a different bargain from the one Google offered two weeks ago, when it put Three-Live on GitHub under Apache 2.0 so developers could inspect what happens to AI generated code before it renders. Both companies want the same workflow, where a model writes the 3D scene and a vendor tool makes it safe to ship. Only one of them lets you audit the sanitizer.
One boundary matters for anyone reading this as an XR story. Snap's Easy Lens documentation says the tool is fully supported on Snapchat and not supported on SPECS, Camera Kit Web or Camera Kit Mobile. This is a pipeline for the phone app, not for Snap's AR glasses, which still have no ship date.
Beyond building, the CLI reports. Snap's page advertises Lens+ insights from the command line, so you can ask your agent which of your published Lenses are performing and decide what to make next. That is the part a studio will care about. The rest is a 1 KB wrapper around a binary you cannot read, moving fast enough to publish four versions in four days. Pin a version before you wire it into anything that matters.
