clerk weekly downloads statistics

clerk

The Clerk command-line interface.

Add Clerk to an app

clerk init is the setup path for developers and coding agents. It detects the framework, installs the matching Clerk SDK for npm-based projects when it is missing, and scaffolds the Clerk wiring it can safely generate.

For accountless-capable frameworks (Next.js, Astro, Nuxt, TanStack Start, and React Router), unauthenticated agent runs can start without a Clerk account or browser login. With no --app and no linked project, a first clerk init run creates an unclaimed development application, writes local development keys, and stores a claim breadcrumb for a later clerk auth login. Later runs keep an existing unclaimed application instead of replacing it, unless you pass --fresh. Frameworks without accountless support need an authenticated app target before keys can be pulled: pass --app , use a linked project, or run npx -y clerk@latest init --login in an interactive terminal to log in and link one.

What clerk init changes:

• Installs missing Clerk SDK packages in npm-based projects. • Creates or updates supported framework files, such as provider wiring, middleware or proxy files, and sign-in/sign-up routes. • Writes Clerk keys to an env file when a real or accountless app is available. • When it creates a new accountless application, writes .clerk/keyless.json and adds .clerk/ to .gitignore. • In npm-based projects, offers to install Clerk agent skills; agent mode runs that step non-interactively unless --no-skills is passed.

After setup, run clerk doctor to verify the integration:

Installation

Homebrew (macOS / Linux)

npm

Usage

Telemetry

The Clerk CLI collects usage telemetry: command name, flag names, duration, outcome, environment signals (OS, install method, terminal), a random machine identifier — and your workspace and app IDs when a project is linked. It never collects command arguments, option values, file paths, or personal data. The first run only shows a disclosure notice and sends nothing (CI environments send from the first run), and clerk --verbose prints every event before it is sent. Shell completion (`clerk completion and the __complete` helper behind Tab) sends nothing at all. See https://clerk.com/docs/telemetry for details.

Opt out with clerk telemetry disable, or by setting CLERK_TELEMETRY_DISABLED=1 (the standard DO_NOT_TRACK=1 also works). clerk telemetry status shows the effective state and why.

Description from the npm listing.