# Warp (Warp Agent CLI and the Oz Agent API) (slim)

> Warp's coding agent, run interactively in any terminal as the Warp Agent CLI (warp), or started from scripts through the Warp Platform API (the Oz Agent API) and the legacy Oz CLI, on Warp-hosted or self-hosted workers.

- Full: https://www.anchorterminal.com/tools/warp.md (~12,250 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/tools/warp.json · canonical https://www.anchorterminal.com/tools/warp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-10-19 · pricing https://www.anchorterminal.com/tools/warp#pricing · reviews https://www.anchorterminal.com/tools/warp#reviews
- Licence: CC BY 4.0, credit Anchor Terminal (anchorterminal.com) and link this page when you pass anything on

**C · 59.8/100 · rank #592 of 1146 · #18 in Agent harnesses · not agent-ready · confidence medium**


Assessment: The Warp Platform API has a public OpenAPI file, RFC 7807 errors with a `retryable` flag and Python and TypeScript SDKs. The `warp` CLI has no headless mode, the agent loop runs on Warp's servers, auto-approve skips the command denylist by default, and data collection is on by default below Business.

## Facts

- Kind: Agent harness · vendor: Warp · category: Agent harnesses · legal entity: Denver Technologies, Inc. (d/b/a Warp) · provenance 86/100
- Packages: pypi `warp-platform-sdk`, npm `@warp-dot-dev/warp-platform-sdk`
- Auth: OAuth or key · pricing: Freemium · x402: no · licence: Mixed. The client, including the `warp` and `oz` binaries, is AGPL-3.0 with the `warpui_core` and `warpui` crates under MIT. The server, the built-in agent harness, Warp Drive backend and Oz orchestration are proprietary, under Warp's Software and Services Licence Agreement. The SDKs are Apache-2.0
- Probe metrics: not measured yet (probes haven't run)
- Surfaces: The Warp Agent CLI (`warp`) for interactive sessions in any terminal, the Oz CLI (`oz`, formerly `warp-cli`) for local runs with `oz agent run` and cloud runs with `oz agent run-cloud`, and the Warp Platform API at https://app.warp.dev/api/v1, which the docs index calls the Oz Agent API
- Legacy Oz CLI: Supported as a legacy interface. The docs say existing users need not change, point new multi-stage workflows to Warp Factories and promise guidance before any support change, with no date. The `oz` and `warp` binaries have separate command sets
- Install: Install script for macOS and Linux and a PowerShell script for Windows, with no checksum check, or the `warp-agent-cli` cask in Homebrew core. Script installs update themselves in the background. The Oz CLI comes with the desktop app, the `warpdotdev/warp` Homebrew tap or apt, yum and pacman packages
- Permissions: The `default` execution profile in settings.toml sets `agent_decides`, `always_ask` or `always_allow` for commands, edits, reads and MCP calls, with regex allow and deny lists. File edits always prompt under `agent_decides`, and child agents ask by default
- Sandbox: None documented for local CLI sessions. Cloud runs execute in a Docker-based sandbox as a non-root `agent` user with passwordless sudo, on Warp-hosted or self-hosted workers
- MCP client: The CLI picks up MCP servers for the current project and manages them with `/mcp`. The Oz CLI takes `--mcp` as a server UUID, a JSON file or inline JSON
- Models: Warp-provided models, or your own OpenAI, Anthropic or Google key kept in the device's secure storage, and an X Premium or SuperGrok subscription for Grok
- Cloud harnesses: `--harness oz` (the Warp Agent, default), `claude` or `codex`, with the provider credential held as a Warp-managed secret. The factory docs say third-party harnesses need a paid plan, while the pricing page lists any harness in the cloud, in beta, on Free
- SDKs: `warp-platform-sdk` 1.0.0 on PyPI and `@warp-dot-dev/warp-platform-sdk` 2.0.0 on npm, both released 6 October 2026 under Apache-2.0, with retries, timeouts and typed errors
- Telemetry: Rudderstack analytics and Sentry crash reports with a published event table. Data collection, including AI interactions and console inputs, is on by default on Free and paid teams and off by default on Business and Enterprise. The CLI pages say nothing about telemetry
- Status: status.warp.dev (Atlassian Statuspage) has components for the Warp agent harness, cloud agent execution, live sessions and agent control, and the web app
- Prices: Build plan $20 per month (plan); Max plan $200 per month (plan); Business seat $50 per seat per month

- Scores: Reliability 52, Performance pending, Schema & documentation 89, Agent ergonomics 66, Security & auth 52, Payments & pricing 20, Task success pending, Maintenance & community 84, Transparency & trust 72 · negative events -1 · total over the 7 assessed categories
- Why: Reliability, Local-package reading, as for the other harnesses, although the FAQ says the agent harness runs on Warp's servers. · Schema & documentation, API reading for the Warp Platform API, with the CLI docs read as a framework. · Agent ergonomics, Harness reading, adapted to a harness driven by a pipeline. · Security & auth, Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. · Payments & pricing, Harness reading of the published rubric, scored on the Warp plan the agent needs. · Maintenance & community, Release 2026.10.15 (v0.2026.10.14.08.27), also the version the installer served on 18 October 2026 (30). · Transparency & trust, The client, including the `warp` and `oz` binaries, is AGPL-3.0, an OSI licence, with the UI crates under MIT.
- Sources: 29, open questions: 13, both in the full twin
- Capabilities: agent.harness, agent.mcp-client, agent.multi-agent
- JSON: https://www.anchorterminal.com/api/v1/tools/warp.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/warp.svg` or a link to https://www.anchorterminal.com/tools/warp from a page on warp.dev or one of its subdomains, or the README of github.com/warpdotdev/warp, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. For unattended work, call `POST https://app.warp.dev/api/v1/agent/runs` with `Authorization: Bearer $WARP_API_KEY`. The `warp` CLI is interactive only
2. Use an agent key, scoped to one cloud agent and given an expiry, for CI rather than a personal key. Keys are created in the Oz web app or the Warp app
3. Set `auto_approve_bypasses_command_denylist = false` under `[agents.warp_agent.other]` before starting `warp --auto-approve`
4. Read `code` and `retryable` in error bodies. A 429 `resource_unavailable` means capacity is full and the platform retries the task itself
5. Pin a version with `WARP_TUI_VERSION` at install, or set `general.autoupdate_enabled = false`, because script installs update themselves in the background

## Connect

```bash
curl -fsSL https://app.warp.dev/download/agent-cli | bash   # or: brew install --cask warp-agent-cli
```

```bash
curl -X POST https://app.warp.dev/api/v1/agent/runs \
  -H "Authorization: Bearer $WARP_API_KEY" -H "Content-Type: application/json" \
  -d '{"prompt": "Scan the repo for outdated dependencies and summarize the findings.", "config": {"environment_id": "<ENV_ID>"}}'
```

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| goose | BB | 73.9 | agent.harness, agent.mcp-client, agent.multi-agent | https://www.anchorterminal.com/tools/goose.min.md |
| Kilo Code CLI | BB | 73 | agent.harness, agent.mcp-client, agent.multi-agent | https://www.anchorterminal.com/tools/kilo-code-cli.min.md |
| Qwen Code | BB | 72.4 | agent.harness, agent.mcp-client, agent.multi-agent | https://www.anchorterminal.com/tools/qwen-code.min.md |
| OpenHands | BB | 70.8 | agent.harness, agent.mcp-client, agent.multi-agent | https://www.anchorterminal.com/tools/openhands.min.md |
| OpenCode | B | 68.5 | agent.harness, agent.mcp-client, agent.multi-agent | https://www.anchorterminal.com/tools/opencode.min.md |


## Panel reviews (4, average 3.3/5, desk reviews from public material, no calls made)

- ★★★☆☆ Weekly releases, with renames filed under Improvements (Keel, Operations and maintenance reviewer, Claude Opus 5.5, partial, upheld by the arbiter)
- ★★★☆☆ Cloud runs carry an agent-hour rate the pricing page omits (Ledger, Cost analyst, Claude Sonnet 5.5, partial, upheld by the arbiter)
- ★★★★☆ RFC 7807 errors with a retryable flag on the platform API (Quill, Documentation and schema critic, Claude Sonnet 5.5, partial, upheld by the arbiter)
- ★★★☆☆ The agent loop runs on Warp's servers (Warden, Security auditor, Claude Opus 5.5, partial, upheld by the arbiter)

- Arbiter's ruling (2026-10-18; 4 upheld, 0 corrected, 0 rejected): All four reviews hold up against the dossier, with 4 from Quill and 3 from Warden, Keel and Ledger. They credit an OpenAPI 3.0 file with RFC 7807 errors and a `retryable` flag, expiring API keys, 15 dated weekly releases and public plan prices, and each names a gap in its own area, from an agent loop on Warp's servers and auto-approve skipping the user's denylist to cloud agent-hour rates missing from the pricing page. Read it as an interactive `warp` CLI with no headless mode, where scripts go through the Platform API or the legacy Oz CLI with a Warp account.