Warp Agent CLI overview

The Warp Agent CLI brings the Warp Agent from the Warp app to the terminal you already use, whether that’s Ghostty, iTerm2, the VS Code terminal, or anything else. Run the warp command to start an agent conversation: prompt the agent in natural language, review and approve its actions, and run shell commands in the same input, without changing your terminal setup.

What is the Warp Agent CLI?

The Warp Agent CLI is a standalone terminal program that runs Warp Agent, the same agent that powers the Warp app. It renders conversations as a scrolling transcript in your terminal, with streaming responses, code diffs, tool calls, and permission requests you approve inline. Because it’s a regular command-line program, it works in any terminal emulator, including over SSH.

To get a working setup in a few minutes, follow the Warp Agent CLI quickstart.

Key features

• Agent conversations - Streaming responses with markdown rendering, file-edit diffs, tool calls, plans, and task lists. See Agent conversations.
• Shell commands - Run shell commands from the same input as agent prompts, including long-running and interactive commands. See Shell commands.
• Permissions you control - Approve commands and file edits from inline request cards, or configure execution profiles and auto-approve. See Permissions and profiles.
• Persistent conversations - Conversations are saved to your Warp account, so you can exit and resume them later or switch between them. See Conversations.
• Cloud handoff and orchestration - Hand a conversation off to a cloud agent, continue cloud runs in the CLI, and coordinate multiple agents. See Cloud and orchestration.
• Project context - The agent picks up your project’s rules (like AGENTS.md), skills, and MCP servers automatically. See Context.
• Model choice - Pick a model per conversation, bring your own provider API keys, and track credit usage. See Models and usage.
• Customization - Configure themes, the statusline, keybindings, and more through a local settings file. See Configuration.

How it relates to the Warp app and Oz

• The Warp app - The Warp Agent CLI runs the same Warp Agent harness as the Warp app, so your account, plan, model access, rules, and skills work the same in both. The CLI doesn’t require the Warp app to be installed.
• Oz - Oz is Warp’s programmable platform for running and coordinating agents at scale. The Warp Agent CLI connects to the same platform: conversations sync to your Warp account, and you can hand work off to cloud agents or continue a cloud run from your terminal.

Supported platforms

The Warp Agent CLI runs on:

• macOS - Apple Silicon and Intel.
• Linux - x64 and Arm64.

Logging in and out

The first time you run warp, the CLI signs you in with a device authorization flow: it shows a verification link and code, opens your browser, and unlocks automatically once you approve the login. For non-interactive environments such as CI, authenticate with a Warp API key instead, using the --api-key flag or the WARP_API_KEY environment variable. See logging in in the quickstart for the full flow.

To sign out, run /logout. The CLI returns to its login screen and opens Warp’s web sign-out page so your browser session is signed out too.

Automatic updates

The Warp Agent CLI keeps itself up to date. While it runs, it periodically checks for a newer version, downloads it in the background, and stages it without interrupting your session. The staged version takes effect the next time you launch warp; when an update is ready, the start screen shows an “update installed, restart to apply” notice next to the version. To turn background updates off, set general.autoupdate_enabled to false in the settings file.

Coming from the Warp app

If you already use the Warp app, most of your setup carries over. Rules and skills are discovered from the same shared paths, and your Warp Drive content syncs after you log in. For the rest, the Warp Agent CLI ships with a bundled migration skill: ask the agent to migrate your setup from the Warp app, and it walks you through copying compatible settings and global MCP server configurations. Credentials are never copied, so MCP servers that require authentication must be reauthenticated in the CLI.

Open source

We plan to open source the Warp Agent CLI. Follow the Warp blog for announcements.

Next steps

• Quickstart - Install the CLI, log in, and run your first prompt.
• Agent conversations - Learn how the transcript, diffs, and approvals work.
• Shell commands - Run shell commands alongside agent prompts.
• Configuration - Customize the CLI with the settings file.
• Reference - Flags, slash commands, and keyboard shortcuts.