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

> Paseo scores 62.1 (B) to Warp's 57.6 (C) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/paseo-vs-warp.md (~6,400 tokens) · this version ~2,380 tokens · JSON https://www.anchorterminal.com/compare/paseo-vs-warp.json · canonical https://www.anchorterminal.com/compare/paseo-vs-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-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Paseo scores 62.1 (B) on agent readiness against Warp (Warp Agent CLI and the Oz Agent API)'s 57.6 (C), and leads in 3 of 7 scored categories. Warp (Warp Agent CLI and the Oz Agent API) leads on schema & documentation and maintenance & community. Both do agent harnesses.

- Paseo: B 62.1, rank #577 of 1510 · https://www.anchorterminal.com/tools/paseo.min.md
- Warp (Warp Agent CLI and the Oz Agent API): C 57.6, rank #786 of 1510 · https://www.anchorterminal.com/tools/warp.min.md
- Paseo, good for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere. Ahead on Security & auth, 58 against 52; Payments & pricing, 60 against 20. Also No key needed to call it; No incidents deducted, where Warp (Warp Agent CLI and the Oz Agent API) loses 3 points for them.
- Warp (Warp Agent CLI and the Oz Agent API), good for Teams that want one agent across an interactive terminal session and API-started cloud runs, including Claude Code and Codex runs on Warp's infrastructure or their own workers. Ahead on Schema & documentation, 89 against 65; Maintenance & community, 84 against 75.

| Category | Paseo | Warp (Warp Agent CLI and the Oz Agent API) |
| --- | --- | --- |
| Reliability (16%) | 50 | 52 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 65 | 89 |
| Agent ergonomics (13%) | 70 | 66 |
| Security & auth (14%) | 58 | 52 |
| Payments & pricing (10%) | 60 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 84 |
| Transparency & trust (7%) | 68 | 69 |

| Fact (where they differ) | Paseo | Warp (Warp Agent CLI and the Oz Agent API) |
| --- | --- | --- |
| Vendor | Mohamed Boudra | Warp |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| Licence | Apache-2.0 | 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 |
| llms.txt | no | yes |
| Last release | 2026-11-07 | 2026-10-15 |
| Terms last updated | no document linked | 2025-10-07 |
| Privacy policy last updated | no document linked | 2026-08-18 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Payments & pricing, Paseo +40: Paseo 60 (Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60.); Warp (Warp Agent CLI and the Oz Agent API) 20 (Harness reading of the published rubric, scored on the Warp plan the agent needs. No payment protocol (0). Plan prices are public, and Warp-provided inference is billed at public API rates on paid plans, but the agent-hour platform rate and compute rate for cloud runs were not on the pricing page (10). Free is $0 and includes Warp Agent CLI access, but no bundled Warp inference, so the agent runs only with purchased usage or your own provider key. Whether sign-up asks for a card was not tested (10). A person signs in through a browser or device code, and API keys are created by hand in the Oz web app or the Warp app (0). 0 + 10 + 10 + 0 = 20. Warp's terms bar any robot, scraper or other automated means to access its Services, so this run pauses its hosts and the readings from warp.dev pages are per the 18 October check, not re-read on 4 November.)
- Schema & documentation, Warp (Warp Agent CLI and the Oz Agent API) +24: Paseo 65 (Harness reading. Public docs, a CLI and plugin examples in the repository (65).); Warp (Warp Agent CLI and the Oz Agent API) 89 (API reading for the Warp Platform API, with the CLI docs read as a framework. docs.warp.dev/openapi.json is OpenAPI 3.0.0 with 293 component schemas and bearer authentication (25). llms.txt with per-section Markdown bundles, including one for the Warp Agent CLI and one for the Automation Platform (10). The run request schema says when each field applies (prompt unless a skill is given, `on_behalf_of` only for agent keys on team runs), and the CLI permissions page states each default and when auto-approve bypasses the denylist (15). Run modes, states and permission values are enumerated, and request bodies are typed objects (13). Curl and SDK examples throughout, and an error catalogue of RFC 7807 bodies with a machine-readable code, `retryable` flag and trace ID per error (14). The API sits under /api/v1 with info version 1.0.0, and the weekly changelog has an Oz updates section, but there is no API-only changelog (12). 25 + 10 + 15 + 13 + 14 + 12 = 89. Warp's terms bar any robot, scraper or other automated means to access its Services, so this run pauses its hosts and the readings from warp.dev pages are per the 18 October check, not re-read on 4 November.)
- Maintenance & community, Warp (Warp Agent CLI and the Oz Agent API) +9: Paseo 75 (v0.15.3 and commits on 7 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current builds (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.); Warp (Warp Agent CLI and the Oz Agent API) 84 (Every dated source of the vendor's own looked for. The weekly changelog (per the 18 October check, not re-read on 4 November) dated release 2026.10.15 (v0.2026.10.14.08.27), 20 days before the check (30). Homebrew's warp-agent-cli cask moved to 0.2026.10.21.08.25.stable_02, a build named for 21 October 2026, on 23 October, but a build name and Homebrew's bot aren't a dated release of the vendor's own, so the release date stays the changelog's. The repository's own release tags and stable branches stop at June 2026. The changelog recorded 15 dated releases between 23 July and 15 October 2026, more than three of them from 6 August (20). Issues and pull requests are public on GitHub. The 18 October counts came through shields.io badges and are struck. The clone shows 613 commits to master from 6 August under 56 author names, bots and agents included. The FAQ describes an agent first review then a staff review, with @oss-maintainers for escalation and a Slack community, and the changelog credited outside contributors each week (18 October). Maintainer reply times are unread (12). Official Python and TypeScript SDKs, released 6 October 2026 as 1.0.0 and 2.0.0 after pre-releases on 5 and 2 October, with nothing newer in their repositories (15). CI on every pull request and a checksummed Homebrew cask, but the install script verifies nothing (7). 30 + 20 + 12 + 15 + 7 = 84.)
- Security & auth, Paseo +6: Paseo 58 (Harness reading. The README says no telemetry, tracking or forced log-ins (30 of 30). Worktree per agent, on your own machine (10 of 20). No prompt-injection guidance (5). No audit log (5). SECURITY.md (8). 30 + 10 + 5 + 5 + 8 = 58.); Warp (Warp Agent CLI and the Oz Agent API) 52 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. The FAQ says the built-in harness runs server-side, so prompts, file contents and command output pass through Warp. The privacy page says AI interactions and console inputs may be collected unless Help improve Warp is off, and the security overview says data collection is on by default for Free and paid teams and off on Business and Enterprise. The opt-out is documented in the desktop app's settings, not for the CLI. Personal and agent keys can expire after 1, 30 or 90 days, and provider keys stay in the device's secure storage (14). Per-action permissions with `always_ask`, `agent_decides` and `always_allow`, edits always shown as a diff under `agent_decides`, a default denylist and child agents asking first. Auto-approve bypasses the user's denylist by default, and no local OS sandbox is documented. Cloud runs use a Docker sandbox as a non-root user with passwordless sudo (11). No prompt-injection guidance was found in the CLI, platform or factory pages read, and secret redaction is off by default (4). Cloud runs record transcripts, tool calls and logs, the API returns timelines and conversations, the app has a Network Log, and the Enterprise Analytics API can filter tool calls for audit (11). SECURITY.md names security@warp.dev and private GitHub advisories, SOC 2 Type II is stated with a trust centre and a subprocessor list. No security.txt and no bug bounty were found, and the GitHub advisory list was not read (12). 14 + 11 + 4 + 11 + 12 = 52. Warp's terms bar any robot, scraper or other automated means to access its Services, so this run pauses its hosts and the readings from warp.dev pages are per the 18 October check, not re-read on 4 November.)