Install the CLI
Install @1claw/cli, log in with the browser device flow, and confirm access with whoami and vault list.
The CLI is the fastest way to work with 1Claw from a terminal. Install it, log in, and you'll have a working authenticated session in under a minute.
Prerequisite: Node 20+ if you install via npm. Homebrew works on macOS and Linux and needs nothing else.
What 1claw setup does under the hood: it calls POST /v1/onboarding/provision, which creates the welcome bundle (a default vault, examples/hello, an MCP agent, and a ** read/write policy) and returns a one-time ocv_ agent key plus a ready-to-paste mcp_stdio_config. Track progress any time with GET /v1/org/onboarding/status. The manual steps below are the same thing, done by hand.
- 1
Fastest path: one command.
1claw setupprovisions adefaultvault, anexamples/hellosecret, an MCP agent, and a read/write policy, then writes MCP config for Cursor, Claude Desktop, and VS Code. Run it and skip to the last step.bashnpx @1claw/cli setup - 2
Install the CLI with npm (needs Node 20+) or Homebrew.
bashnpm install -g @1claw/cli # or brew install 1clawAI/tap/oneclaw - 3
Log in. This opens your browser to 1claw.co, you approve, and the CLI polls until you confirm. No password typed in the terminal.
bash1claw login - 4
Confirm who you're logged in as.
bash1claw whoami - 5
List your vaults to prove the session reaches the API.
bash1claw vault list
If you already exported ONECLAW_API_KEY in Lesson 1, you can skip browser login and use that key instead (see the CI tip below).
For CI or any non-interactive shell, skip login and set env vars instead: export ONECLAW_TOKEN="your-jwt" or export ONECLAW_API_KEY="1ck_..." (add ONECLAW_VAULT_ID for vault-scoped commands).
The CLI is installed and authenticated. 1claw whoami and 1claw vault list both work, so you're ready to create vaults and secrets from the terminal.
Check your understanding
3 questionsWhat Node version does the npm install of the CLI require?
What does 1claw login use so you never type a password in the terminal?
Which env var lets the CLI run non-interactively with a personal API key in CI?