Skip to main content
AI Choice EngineAI Choice Engine
Browse decision tools
← All setup guides

Warp · Setup guide

How to set up Warp Agent CLI

Install Warp’s standalone Agent CLI in the terminal you already use, verify it, sign in with the browser device flow, and begin with a small approval-first task. The same account can connect the CLI to Warp’s models and Warp Drive context, while managed credits, BYOK, and cloud agents have different privacy and billing boundaries.

Warp Agent CLI

terminal · checked August 14, 2026

~10 minBeginner
Start installOpen Warp Agent CLICompare itBuyer guide

The “Open Warp Agent CLI” link goes to the vendor site. It is not an affiliate-tracked link on this page — no commission is claimed for that click. Affiliate disclosure.

Critical: finish install before closing the window

Keep the installer terminal open until you see a success message. If you used an admin window, do not close it until verification works. Then open a new Terminal or PowerShell window and run the verify step — PATH updates rarely apply to shells that were already open, especially on Windows.

Before you begin

  • macOS, Linux, or Windows with a supported terminal.
  • A Warp account for the browser sign-in flow.
  • A small git repository or disposable clone with secrets removed.
  • A provider API key only if you plan to use BYOK instead of Warp-managed inference.

Authentication

Browser device login when you first run warp

Account: Warp account; a Warp plan, credits, or supported BYOK provider for agent inference

Run warp and approve the verification link and code in your browser. On a browser-less machine, use WARP_API_KEY through the environment rather than putting a key in command history.

Install or open it

1. Get the harness ready

These steps are written for beginners. On Mac, Terminal is the black/white text window where you type commands. On Windows, use PowerShell or Terminal. Use the OS tabs to hide steps that are not for your computer, then copy one command at a time.

  1. 01

    Open Terminal on a Mac

    Mac

    Click the Spotlight search icon (magnifying glass) at the top-right of the menu bar, or press Command (⌘) + Space. Type Terminal and press Return. A text window opens — that is where you paste the install commands below. Leave it open.

  2. 02

    Open Terminal or PowerShell on Windows

    Windows

    Press the Windows key, type Terminal or PowerShell, then press Enter. Use that window for the commands below. If Windows asks for permission to run a script or install software, read the prompt before approving.

  3. 03

    How to paste a command

    Copy one command at a time from this page. Click inside the terminal window, paste (Mac: ⌘+V, Windows: Ctrl+V or right-click → Paste), then press Return / Enter. Wait until the prompt comes back before running the next command. You do not need to type the leading $ if you see one in other docs.

  4. 04

    Do not close the installer until verified

    Keep the installer terminal (or admin PowerShell) open until the install finishes without errors. Closing early can leave a half-written binary or an incomplete PATH update — especially on Windows.

  5. 05

    Open a new terminal after installers

    PATH updates often only apply to new shells — especially on Windows. Do not close the install session until the installer finishes, then open a fresh Terminal/PowerShell before running --version checks.

  6. 06

    Inspect before you pipe an installer

    Commands like curl … | bash download and run a script immediately. Prefer the official package manager when offered. If you use a curl installer, you can download the script first, open it in a text editor, then run it — never paste installers from random blogs.

  7. 07

    Install the Warp Agent CLI on macOS or Linux

    Paste the official Agent CLI installer into Terminal, then open a fresh terminal before checking the command. This brings Warp Agent to an existing terminal; it is not the full Warp desktop app.

    bash
    curl -fsSL https://app.warp.dev/download/agent-cli | bash

    You should see: The installer finishes without an error. Open a new terminal before the verify step so PATH updates apply.

    If this fails
    • The install command errors, or the next verify step says “command not found”. Re-run the official install command with network access, then open a brand-new terminal window before verifying.
    Warp Agent CLI quickstart
  8. 08

    Install the Warp Agent CLI on Windows

    Windows

    Run the official PowerShell installer and reopen PowerShell when it finishes so the PATH update is applied.

    powershell
    Invoke-RestMethod "https://app.warp.dev/download/agent-cli.ps1" | Invoke-Expression

    You should see: The installer finishes without an error. Open a new terminal before the verify step so PATH updates apply.

    If this fails
    • The install command errors, or the next verify step says “command not found”. Re-run the official install command with network access, then open a brand-new terminal window before verifying.
    Warp Agent CLI quickstart
  9. 09

    Optional: install the full Warp terminal app on a Mac

    Mac

    If you want Warp Drive’s full terminal UI rather than only the standalone Agent CLI, install the official desktop app separately. Do not install both paths just to fix a missing CLI command.

    bash
    brew install --cask warp

    You should see: The installer finishes without an error. Open a new terminal before the verify step so PATH updates apply.

    If this fails
    • The install command errors, or the next verify step says “command not found”. Re-run the official install command with network access, then open a brand-new terminal window before verifying.
    Warp installation
  10. 10

    Verify Warp Agent CLI

    Run the version check in a new terminal. The command should print the installed CLI version before you sign in.

    bash
    warp --version

    You should see: Warp prints the installed version. If missing, open a new terminal and confirm the official installer completed.

    If this fails
    • warp: command not found after installation. Open a new terminal first. If it still fails, rerun the official Agent CLI installer and check the PATH directory it reports; installing the Warp desktop cask is not a substitute for the CLI check.
    Warp Agent CLI reference

Repository or project

2. Start in the right place

Keep the first repository small, clean, and easy to roll back while you learn the harness’s permissions and context model.

  1. 01

    Enter the practice repository

    Use a clean branch or disposable clone. Warp Agent can read files, run shell commands, and edit the working tree, so keep production credentials out of the first session.

    bash
    cd path/to/your-repository

    You should see: The prompt shows you are inside the intended folder (check with `pwd`).

    If this fails
    • “No such file or directory” or you are still in your home folder. Create or clone the practice folder first, then `cd` into it before starting the tool.
  2. 02

    Start Warp and sign in

    Run the CLI. Follow the browser verification link and wait for the start screen before sending a prompt.

    bash
    warp

    You should see: The tool starts in this folder and waits for your first prompt (or shows a short first-run / sign-in screen).

    If this fails
    • Nothing happens, or you land in the wrong folder. Confirm you are inside the practice repo (`pwd`), that you signed in, and that you opened a new terminal after install.
    Warp Agent CLI quickstart
  3. 03

    Review provider keys before the first request

    Inside the session, open the API-key menu and confirm whether the request will use a provider key, Warp credits, or a fallback route.

    bash
    /api-keys

    You should see: The shell accepts the command with no error so the next step can use the credentials or provider.

    If this fails
    • Auth fails, the key is rejected, or the provider list is empty. Confirm the key/account is active, that you pasted the whole value, and that you are using the shell syntax for your OS (export vs $env:).
    Warp models and usage

First run

Approval-first repository orientation

Use this task to test the workflow before handing over a larger repository or production responsibility.

  1. 01Start from a clean practice repository and keep the default approval prompts enabled.
  2. 02Ask Warp Agent to explain the entry points and test command, and to propose a one-file documentation change without applying it.
  3. 03Review the plan, then allow only the tiny docs change; run git diff and the repository’s tests before accepting anything broader.

Why this is safe: Warp’s approval flow lets a beginner see the agent’s proposed shell and file actions before a mutation, while a clean branch keeps rollback simple.

Stop and review if

  • The agent tries to run a destructive shell command or access credentials without a clear reason.
  • The session uses Warp credits or a cloud agent when you intended a BYOK/local route.
  • A prompt, rule, MCP server, or Warp Drive item comes from an untrusted workspace.

The operating boundary

Privacy, data, and cost

The setup is incomplete until you know what the harness can see, what account pays for it, and who approves a risky action.

Privacy

Warp markets Zero Data Retention on Business and Enterprise plans, not every seat. Telemetry, cloud-agent transcripts, and BYOK endpoints still follow separate controls; confirm the live plan language and managed-provider contracts before regulated workloads.

Training on code: tier dependent

Warp’s control plane and any cloud-agent execution path can still process code context. BYOK and custom endpoints follow the provider’s retention terms. ZDR on Warp-managed inference is advertised for Business/Enterprise — still confirm contractual language in writing for regulated use.

Sensitive repos: Disable optional telemetry or Help Improve Warp when policy requires it, keep approval mode on, use a sanitized clone, and have an admin review cloud-agent and team data controls before production code.

Pricing

Warp’s terminal has a free path, while Agent requests can use plan credits, add-on pay-as-you-go credits, or supported BYOK provider keys. Cloud-agent runs can draw from the account or team credit pool.

Model: hybrid

Watch out: Free terminal access does not guarantee bundled Agent inference. Check the selected model, credit fallback, BYOK key, and cloud-agent destination before a long task. Claude Fable 5 and Opus 5 are 50% off for a limited time with no published end date — confirm the live Warp billing page before a pilot.

Estimate a seat stack

When setup goes wrong

  • warp: command not found after installation.

    Open a new terminal first. If it still fails, rerun the official Agent CLI installer and check the PATH directory it reports; installing the Warp desktop cask is not a substitute for the CLI check.

  • The browser does not open during login.

    Copy the verification URL shown by warp into a browser and enter the displayed code. For a headless machine, set WARP_API_KEY in the environment instead of passing a key in shell history.

  • Warp says the Agent has no credits or asks for an upgrade.

    Confirm the active plan and model. Free terminal usage is separate from managed Agent credits; buy add-on credits, use a supported BYOK key, or stop the run before it incurs spend.

  • A BYOK request still consumes Warp credits.

    Open /api-keys, confirm the provider key is valid, and check the credit fallback setting. A failed BYOK request can fall back to Warp-managed credits unless you change that setting.

Next steps

After the first successful run

Keep the pilot small, then compare surfaces and budget before a team rollout.

Compare harnessesBuyer guideOpen-source agents hubAI stack cost calculatorGPU inference (rent)Local GPU sizingBuyer guidesLocal open-source AI guide

Setup details change quickly. The page was checked August 14, 2026; use the official source below before installing in a managed or production environment.

Warp Agent CLI quickstartCompare all harnesses