Grokified CLI — one install, one key

The Grokified CLI installs once (npm install -g grokified), stores your Grokified access key, and launches supported coding agents already pointed at https://api.grokified.cyou/v1. Twelve tools — Cursor, Claude Code, Codex, Cline, Aider, Zed, and more — share one key and one setup flow. This is not xAI Grok Build (x.ai/build / grok.com/build) and not third-party grok-cli GitHub/npm packages.

npm install -g grokified

Need a key or base URL first? Create and manage gk_* keys on Grok API docs, then come back here for login → setup → doctor.

Commands.

Everything the CLI does today. Nine commands — setup is the only one with a picker.

Install and first run

1. Install with the npm, pnpm, bun, or shell tab at the top of this page.
2. Store your key: grokified login, or grokified login --key gk_live_… when no browser is available. Key creation and revocation are in /docs/authentication.Access keys, base URL https://api.grokified.cyou/v1, and the OpenAI-compatible first request live on Grok API docs. This page only stores the key via grokified login / grokified login --key gk_live_… and wires tools — it does not replace the docs key lifecycle.
3. Point tools at Grokified: grokified setup (no argument opens a picker).
4. Confirm wiring before you launch: grokified doctor or grokified status. Relay requirements differ by tool — see the writes table below.
5. Launch a configured tool with grokified run <tool> or your editor’s usual entry point. The full matrix is on /agents.

Command	What it does
grokified login	Signs in through the browser. --key gk_live_… for headless.
grokified logout	Forgets the stored key.
grokified setup [tool…]	Points your coding tools at Grokified. No argument opens a picker.
grokified list	Every tool it can set up, and which are on this machine.
grokified run <tool> […]	Launches a tool already pointed at Grokified.
grokified relay <start\|stop\|status>	The local relay, for tools that speak Anthropic's protocol.
grokified doctor	Is the key live, is the relay up, what is wired to us.
grokified status	Balance, key, active discount.
grokified update	How to get the newest version.

What it writes.

Every tool the CLI can set up, and none of them put your key on disk. For each: the file it touches, how it gets the key instead, and whether it needs the local relay.

Tool	Config file	Key on disk	Needs local relay
Terminal coding agent (grok)	~/.grokified/grok-home/config.toml	No. Passed as an env var at launch.	No.
Claude Code	~/.claude/settings.json	No. Held by the local relay process, not the config file.	Yes. 127.0.0.1:4111
Codex	~/.codex/config.toml	No. Fetched fresh at request time, not stored.	No.
opencode	~/.config/opencode/opencode.json	No. Read from an environment variable.	No.
Crush	~/.config/crush/crush.json	No. Read from an environment variable.	No.
Goose	~/.config/goose/custom_providers/grokified.json	No. Read from an environment variable.	No.
Qwen Code	~/.qwen/settings.json	No. Read from an environment variable.	No.
Aider	~/.aider.conf.yml	No. Read from an environment variable.	No.
Zed	~/.config/zed/settings.json	No. Pasted into Zed's own settings UI, or an env var.	No.
Continue	~/.continue/config.yaml	No. The CLI won't write it — you paste it in yourself.	No.
Cline / Roo Code / Kilo Code	the extension's own settings panel	No. Held in VS Code's encrypted key storage.	No.
Anything else compatible	wherever that tool keeps its settings	No. You paste it in yourself.	No.

faq

CLI questions.

What is the Grokified CLI?

A one-time install that stores your Grokified access key and launches supported coding agents already pointed at https://api.grokified.cyou/v1.

Which agents does it set up?

Twelve targets including the terminal grok agent, Claude Code, Codex, Cursor, Cline / Roo / Kilo, Aider, Zed, and others listed on /agents. Run grokified setup with no argument for a picker.

What should I run after installing the Grokified CLI?

Use the documented login or headless-key path, run grokified setup, then run grokified doctor or grokified status before launching the configured tool. For API host and key details, see Grok API docs at /docs.

Where do I get an access key?

See /docs for base URL, gk_* keys, authentication, and your first API request — or run grokified login to sign in through the browser. Current prepaid usage and live offer information is on /pricing.

How do I update the Grokified CLI?

Run grokified update — it prints the reinstall command for your package manager from the live command reference on this page. Your stored key survives the upgrade.

Is the Grokified CLI the same as open-source grok-cli on GitHub or npm?

No. Those are separate projects. The Grokified CLI is the grokified npm package that stores your Grokified gk_* key and runs grokified setup to point supported agents at https://api.grokified.cyou/v1. Install with the commands on this page; do not confuse it with third-party grok-cli packages.

Is this the same as Grok-Build?

No. /cli is the Grokified npm CLI that configures many coding agents for the prepaid Grokified gateway. Official xAI Grok Build lives at x.ai/build / grok.com/build and is a different product. For the terminal grok / Grok-Build agent wired with a Grokified key specifically, see /grok-build. Grokified is independent and is not xAI.

Where are full docs?

See /docs for the API quickstart and /agents for every tool the CLI configures.

See every tool it reaches.

What is configured today, what still takes a few manual steps, and the three tools nothing on our side can reach.

See every agent Read the quickstart

Start from home if you are new to Grokified, use docs for keys and first API call, and use agents for the full setup matrix. Current prepaid usage stays on pricing.