> For the complete documentation index, see [llms.txt](/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Warp Agent CLI quickstart

Install the Warp Agent CLI, log in, and run your first agent conversation in your own terminal in a few minutes.

This guide takes you from installing the Warp Agent CLI to your first agent conversation in about five minutes.

## Prerequisites

-   **A Warp account** - The login step opens your browser, where you can sign in or create an account. The CLI uses the same account as the Warp app.
-   **A supported platform** - macOS or Linux. See [supported platforms](/cli/#supported-platforms).

## Install the Warp Agent CLI

Note

Install instructions will be published when the CLI is released. If you’re testing a pre-release build, use the install link shared with you.

After installing, verify that the `warp` command is available:

```
warp --version
```

The command prints the installed version. The CLI keeps itself up to date automatically after this; see [automatic updates](/cli/#automatic-updates).

## Log in

Log in once so the CLI can access your Warp account, models, and saved context.

1.  Run `warp`.
2.  The CLI shows a verification link and a device code, and opens the link in your browser. If the browser doesn’t open, visit the link shown in the CLI and enter the code.
3.  Approve the login in your browser. The CLI unlocks automatically, so you don’t need to restart it.

When login completes, the CLI shows its start screen: the version, a short “What’s new” list, and the rules, skills, and MCP servers it discovered for your current directory.

Note

On machines without a browser, such as CI or remote servers, authenticate with a Warp API key instead by setting the `WARP_API_KEY` environment variable:

```
WARP_API_KEY=YOUR_API_KEY warp
```

You can also pass the `--api-key` flag, but prefer the environment variable: command-line arguments can be captured in shell history and process listings. See [API keys](/reference/cli/api-keys/) for how to create one.

## Run your first prompt

1.  Type a prompt in plain language, for example: `What does this project do?`
2.  If the agent wants to run a command or edit a file, it shows a permission request. Choose an option to approve or reject the action.

Learn more about the transcript, diffs, and approvals in [Agent conversations](/cli/agent-conversations/) and [Permissions and profiles](/cli/permissions-and-profiles/).

## Run a shell command

You can run shell commands directly without leaving the CLI.

1.  Type `!` at the start of an empty input to switch to shell mode. The footer shows **Shell mode**.
2.  Type a command, such as `git status`, and press `Enter`.
3.  Press `Backspace` on the empty input to switch back to prompting the agent.

See [Shell commands](/cli/shell-commands/) for long-running commands, interactive programs, and natural language detection.

## Exit and resume

1.  Press `Ctrl+C` twice in a row to exit, or run `/exit`. A single `Ctrl+C` press stops the agent’s current response, or clears the input when nothing is running.
    
2.  On exit, the CLI prints a resume command for the conversation:
    
    ```
    warp --resume CONVERSATION_TOKEN
    ```
    
3.  Run the printed command later to pick up where you left off.
    

To browse and reopen past conversations from inside the CLI, see [Conversations](/cli/conversations/).

## Next steps

-   [Agent conversations](/cli/agent-conversations/) - Work with the transcript, code diffs, plans, and tasks.
-   [Context](/cli/context/) - Give the agent rules, skills, and MCP servers.
-   [Configuration](/cli/configuration/) - Set your theme, statusline, and keybindings.
-   [Reference](/cli/reference/) - All flags, slash commands, and keyboard shortcuts.