Atelier

CLI

The atelier CLI lets you use Atelier as a backend from any editor — Cursor, Claude Code, Codex CLI, OpenCode, Windsurf, plain vim. Studio is one way to build on Atelier; the CLI is the other.

Install

# one-off
npx atelier --version
 
# global
npm i -g @atelier/cli

Sign in

atelier login
# opens atelier.style in your browser; token is stored in your OS keychain

Project lifecycle

# Inside an existing project (any framework)
atelier init                # adds .atelier/ + @atelier/sdk, doesn't touch your code
atelier projects link <id>  # connect to an existing Atelier project
atelier projects list

Local development

atelier dev                 # local dev server + Base bindings

Your existing dev server stays — atelier dev runs alongside and provides the Base primitives (DB, auth, storage, realtime, functions). All @atelier/sdk calls hit a local PGlite during dev.

Database

atelier db migration new add_users
atelier db migrate          # apply pending migrations locally
atelier db push             # apply to production
atelier db pull             # pull production schema into a new migration
atelier db reset            # nuke local DB, reapply all migrations

Deploy & operate

atelier deploy              # canary rollout (5 → 25 → 50 → 100)
atelier deploy --skip-canary
atelier rollback
atelier deployments list
atelier logs --tail
atelier logs --function process-order --since 1h

Env & secrets

atelier env list
atelier env set STRIPE_KEY=...
atelier secrets set --from-file .env.production

Secrets are encrypted at rest and only decrypted inside Functions or during the build step. Never exposed to the browser.

Use with AI editors

The CLI is designed to be invoked from agents. In Cursor, Claude Code, Codex CLI, OpenCode, or Windsurf:

“Run atelier deploy and watch the logs”

The agent calls atelier deploy --json (machine-readable output), parses the result, then calls atelier logs --tail --json. No code changes needed in your project.

For tighter integration, see MCP — the AI agent calls Atelier directly through Model Context Protocol tools.

See also