Clerk's CLI and accountless setup: adding auth without signing up

For years, adding Clerk to an app started in a browser. You signed up, created an application in the Dashboard, copied two keys and pasted them into an environment file. On 30 September 2026, Clerk removed all of those steps for new Next.js projects.

It is the latest release in a run that began in April, when Clerk launched its command-line tool. This article covers what accountless setup does and how the CLI got there.

Accountless setup: what it does

Run this in a Next.js project while signed out of the Clerk CLI:

npx clerk@latest init

Clerk says the command "detects your framework, installs the SDK, scaffolds the integration, and writes your keys in one command." When you are signed out, it also "creates an accountless application." The development keys go into .env.local, and the app runs against them. You have Clerk running locally without having visited clerk.com.

When you want to keep the app, there are two more commands:

1. npx clerk@latest auth login signs you in and attaches the unclaimed application to your account.
2. npx clerk@latest deploy creates the production instance.

Clerk's announcement says the feature arrived in @clerk/nextjs 7.8.0, and that 7.9.6 and later show a clearer error when keys are missing.

Why Clerk built it

Clerk's explanation is about AI coding agents: "Agents stall on account creation. Asking you for permission to create an account for a service slows you and your agent down."

An agent building an app can run a terminal command. It cannot easily sign up for a service, confirm an email and copy keys out of a web dashboard. Clerk calls the approach "agent-first, human-ready." The CLI detects when it is running without an interactive terminal and completes setup without stopping to ask questions.

The same thinking went into the error message for missing keys. Clerk writes: "We wrote it for both humans and agents: plain instruction, no jargon, and the exact commands to run." For agents there is also npx clerk@latest doctor --json, which reports what is wrong with a project in a structured form.

Six months of CLI releases

The CLI itself (22 April). It is open source and installs through npm, bun, pnpm, yarn, Homebrew or curl. clerk init sets up a project, clerk config manages instance settings and clerk api calls Clerk's APIs directly.

clerk deploy (10 June). Going to production with Clerk involves DNS records, OAuth credentials for each social provider and certificate checks. clerk deploy walks through them and can resume if you stop partway. When there is no interactive terminal, it outputs JSON describing what a human still needs to do.

CLI 2.0 (9 July). Two additions are useful for debugging:

• clerk webhooks listen opens a relay tunnel and forwards webhook deliveries to a handler on your machine. clerk webhooks verify checks a signature offline.
• clerk impersonate "creates a short-lived sign-in URL that logs you in as another user, so you can reproduce a report from their exact session."

Clerk also set out what it calls the CLI's agent contract: "stable error codes, stdout for data and stderr for UI, and no hidden interactive prompts in non-TTY contexts."

clerk mcp install (22 July). This registers Clerk's own MCP server with the AI tools on your machine. We cover it in Clerk's agent and MCP auth push.

What to watch out for

• Unclaimed apps are for development only. Clerk states that "Unclaimed applications and development keys are not production-ready." Its announcement does not say how long an unclaimed application is kept, so claim anything you care about.
• Check what the agent created. If a coding agent ran init for you, there may be a Clerk application and a set of keys you did not know about. npx clerk@latest doctor shows the CLI session and project setup.
• Keep .env.local out of version control. The keys are written there automatically. They are development keys, but the habit matters once production keys go in the same place.
• Impersonation is powerful. clerk impersonate signs you in as a real user. On Business and Enterprise plans, Admin Logs record configuration changes. Decide who on your team should hold CLI access.
• Development instances have their own problems. Since 28 September, Apple has been rejecting emails from Clerk development instances. If you test a fresh accountless app with an iCloud address, the verification code will not arrive.

What it means for developers

• Trying Clerk is now much cheaper in time. One command, no account, and you can remove it if you don't like it.
• Local webhook testing no longer needs a separate tunnel tool. That makes it easier to test the delayed-webhook cases described in our review of Clerk's summer incidents.
• The CLI is another way in when the Dashboard is slow. On 1 October the Dashboard had a period of high latency while the APIs were unaffected.
• Cost starts at zero. Development is free, and production is free up to 50,000 retained users. See Clerk pricing in 2026.

When a setup command fails and you are not sure whether it is your network or Clerk, Clerk's live status on isuptime is the quickest check. If your app deploys to Vercel, look there too.

---

Sources

• Accountless setup for Clerk in Next.js (Clerk)
• Introducing Clerk CLI (Clerk)
• Clerk CLI (Clerk changelog)
• Clerk Init: The fastest way to start a new project (Clerk)
• clerk deploy: guided, resumable, agent-ready (Clerk changelog)
• CLI webhooks, impersonation, and a refreshed experience (Clerk changelog)
• Connect your AI tools to Clerk MCP with one command (Clerk changelog)
• Clerk is now available in Stripe Projects (Clerk changelog)