Agents > Context & customization

Models and usage in the Warp Agent CLI

Choose models in the Warp Agent CLI, bring your own API key, and track usage balances and per-response cost.

The Warp Agent CLI gives you the same model options as the Warp app. You can pick the model that powers your conversations, bring your own provider API keys, route requests through custom model routers, and see what every response costs as you work.

Choosing a model

Run /model to open the model picker. You can also click the model name in the statusline to open the same picker.

Models that your plan or your team’s settings don’t allow appear disabled in the picker.

Your choice is saved as the base model of your active profile, so it persists across sessions. See permissions and profiles for how profiles work in the CLI. For the full list of supported models and to learn more about how Warp’s Auto models pick for you, see Model choice.

Bring your own API key

The CLI supports Bring Your Own API Key (BYOK) for OpenAI, Anthropic, and Google models, and can connect an X Premium or SuperGrok subscription for Grok models. Requests routed through your account do not consume Warp-provided inference usage. Applicable platform charges still apply.

Run /api-keys to open the key management menu. It lists each provider with its connection state, plus a Warp credit fallback toggle:

Set a key - Press Enter on OpenAI, Anthropic, or Google and enter the key. Input is masked, so the key never appears in your transcript or shell history, and it’s saved to your device’s secure storage. Warp does not store provider keys on its servers.
Replace or clear a key - On a connected provider, Enter loads the stored key (still masked) for editing, and saving an empty field clears it. Ctrl+X clears the highlighted provider’s key from the list.
Connect X Premium or SuperGrok - Press Enter on the subscription row and the CLI opens your browser to sign in to your xAI account. Ctrl+X disconnects it. Running /connect-grok jumps straight to this row and starts the sign-in.
Warp credit fallback - Press Enter to toggle whether a request that fails through your key is retried with Warp-provided inference, consuming your available usage. See failover and fallback behavior.

You can also store or clear keys outside a session with the --set-provider-api-key and --clear-provider-api-key flags. See the Warp Agent CLI reference. X Premium/SuperGrok connections can only be managed from inside a session, with /api-keys or /connect-grok.

Custom model routing

Custom routers appear in the /model picker alongside individual models. Select one and each prompt resolves to a concrete model using the routing logic you defined.

The CLI loads the same router definitions as the Warp app. These are YAML files in ~/.warp/custom_model_routers/, plus any team-synced routers your admin shares. Authoring a router as a file documents the file format.

Usage and cost

The CLI shows usage at three levels:

Account usage - Run /usage to open a read-only panel with your current account or workspace’s plan, balances, consumption, and billing links. Press Esc to close it. This is not conversation-level usage.
Conversation total - Once usage is reported, the statusline shows the conversation’s accumulated usage. Click the entry to switch between dollars and credits when both display options are available.
Per-response details - Run /cost to hide or show the latest completed response’s elapsed time and credits. This summary does not follow the statusline’s dollar-display preference.

Model choice - Supported models and how automatic model selection works.
Bring Your Own API Key - How BYOK works, key storage, and billing behavior.
SuperGrok subscription - Use Grok models through your xAI account.
Custom routers - Define routing logic that picks a model per task.
Warp Agent CLI reference - Flags and slash commands, including the API key commands.