Emdash vs Warp (Warp Agent CLI and the Oz Agent API)

Emdash 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.

Emdash 55

Harness reading. Docs site and a workspace server package (55).

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.

Emdash 54

Apache 2.0 (30). A telemetry page on the docs site (not read) (18 of 30). No deprecation policy (5). Disclosed with an opt-out (15 of 20). 30 + 18 + 5 + 15 = 68.

Warp (Warp Agent CLI and the Oz Agent API) 69

The client, including the warp and oz binaries, is AGPL-3.0, an OSI licence, with the UI crates under MIT. The built-in agent harness, the server and Oz orchestration are proprietary, so the part that runs the agent loop is closed. Judgement call (20). The privacy page says Business and Enterprise are covered by zero data retention, the security overview says ZDR applies across all plans and elsewhere mentions it for Enterprise teams, and the legal security page says it is available on the Enterprise plan. The privacy notice gives criteria rather than retention periods. A subprocessor list and a DPA are linked (15). The Oz CLI carries a legacy notice with a promise of guidance before any support change, and the changelog dates renames such as warp-tui to warp, but there is no written deprecation policy or notice period (8). An exhaustive telemetry event table, Rudderstack and Sentry named, and an opt-out in the app's privacy settings. The CLI pages don't describe what the CLI sends or how to switch it off (14). 20 + 15 + 8 + 14 = 57. 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.

Emdash 38

Harness reading. Telemetry is described as optional and disabled in Settings or with TELEMETRY_ENABLED=false, which reads as on by default (15 of 30). Worktree per task and remote machines over SSH (10 of 20). No prompt-injection guidance (5). No audit log (5). No security policy file found (3). 15 + 10 + 5 + 5 + 3 = 38.

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.

Emdash 70

v1.2.11 on 6 November 2026 (30). v1.2.9, v1.2.10 and v1.2.11 within two weeks (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current installers and Homebrew cask (15). Release workflows, no test CI (5). 30 + 20 + 0 + 15 + 5 = 70.

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.

Emdash 55

Harness reading. Issue intake from Linear, GitHub, Jira and others, diff review, pull requests and CI checks in one place, local or over SSH (55).

Warp (Warp Agent CLI and the Oz Agent API) 66

Harness reading, adapted to a harness driven by a pipeline. MCP servers are attached per run with --mcp or the mcp_servers config, and profiles gate MCP calls, but no per-tool disabling or deferred tool loading was found (12). The API lists runs with limit, cursor, sort_by, state, task_status and name, and returns a normalised conversation and a timeline per run. The warp CLI has no print mode or JSON output and the Oz CLI's run output is described only as printed tool calls (12). RFC 7807 errors with codes such as insufficient_credits and budget_exceeded, a retryable flag, and since 7 October 2026 unattended CLI runs end as blocked instead of hanging when the agent asks for input. No CLI exit codes are documented (16). Follow-ups, interrupts and cancels by run or conversation ID, conversation_id to continue a run, and warp --resume. No idempotency key on run creation (14). Python and TypeScript SDKs with retries and timeouts, but a cloud run needs an environment ID and a Warp account with usage, and the warp CLI itself can't be driven headless (12). 12 + 12 + 16 + 14 + 12 = 66. 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.