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

AXLR 60

No payment protocol (0). Free and Apache-2.0 with nothing to buy, so 20, 20 and 20 on the last three lines by the self-hosted rule, since the docs say what you pay your model provider, the free route needs no card, and it runs local models with no signup at all, the JSON worker without any model. 0+20+20+20 = 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.

AXLR 70

Read as a local package, as claude-code, goose, opencode and openhands were. Release archives for Linux, macOS and Windows on amd64 and arm64 with a .sha256 beside each, a GHCR image, an OCI Helm chart and source builds with Go 1.26, all stated in the docs; no Homebrew, npm or apt route (20). CI on main runs vet, race tests and a coverage gate above 80 per cent for both modules, with the sandbox tests required under bubblewrap, and the last ten runs on main to 1 November 2026 all passed; the release workflow tests on six native runners (25). 10 open issues, all opened by the founder on 19 and 21 October 2026 as trackers for service work (work modes, plugins, the sandbox setting, cost limits), none from an outside user and none a crash report, 0 open pull requests and about 100 merged; with 0 stars there is nobody else to report, so the handling of outside reports is untested (20). Tags are semver 0.x and the docs date each behaviour change inline ("until 14 October 2026…"), but the 21 releases have empty notes, there is no CHANGELOG.md, and the product contract records one retirement (the seven 1.0 skill definitions on 5 October 2026) without a notice period (5). Pre-1.0, which the README calls an evolving project (0). 20+25+20+5+0 = 70.

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

Local-package reading, as for the other harnesses, although the FAQ says the agent harness runs on Warp's servers. An install script for macOS and Linux and a PowerShell one for Windows, with supported systems stated (macOS, Linux x64 and Arm64, Windows x64 and Arm64), and a warp-agent-cli cask in Homebrew core that carries a SHA-256. The script itself checks no checksum (18). The repository's Warp CI workflow runs cargo nextest, doc tests, clippy and release-compilation checks on every pull request to master. The repository has 23 workflow files. Whether CI passes on the default branch could not be read (15). Per our GitHub record (read 18 October 2026), the tracker had 3.9k open issues against 7.1k closed, and 1.5k open pull requests against 3.8k closed. How many open issues are crashes or regressions, and how fast they get replies, could not be read. The weekly changelog records crash fixes in most releases, such as two crash fixes on 7 October 2026 (10). Weekly dated releases with versions such as v0.2026.10.14.08.27 and no breaking-change heading. The binary rename from warp-tui to warp on 23 July 2026 sat under Improvements (4). Version 0.x with date-based numbers. A stable channel is named and the CLI pages carry no beta label (5). Not scored on this reading. status.warp.dev has components for the agent harness and cloud execution, and logged scheduled cloud agents unavailable for about 2.5 hours on 16 October and session sharing degraded for about 4.75 hours on 30 September 2026. The docs say Warp has no formal SLA. 18 + 15 + 10 + 4 + 5 = 52.

AXLR 83

Harness reading of the framework line, scored on what a program driving it has to supply. Six local tools plus the host's bookkeeping tools; work modes and an execution policy hide the tools a run may not use, axlr_catalog searches the catalog instead of loading it, forged tools keep the request prefix for the prompt cache, and a context cap of 75,000 prompt tokens opens a successor session (20). local_read, local_search and local_list page with offset, next_offset and max_bytes; StreamEvents takes after, max_events (1 to 256) and wait_ms; a budget per execution in seconds, requests, tool calls and dollars; 32 tool calls a turn and max_session_usd (20). The --exec run ends in one result line with a status, the pending call, every call's outcome and the usage, and exits 0, 3 or 1; service errors carry codes an agent can act on; a budget stop says which limit (budget: requests 20 reached) and leaves the session resumable (16). Idempotency-Key on every turn, approval and direct call with cross-transport replay, expected_revision on decisions, expected_sha256 on worker writes, and an interrupted effectful call left uncertain for an operator rather than retried (19). One command runs a task, but the first launch needs an OpenRouter key or a local server, the service needs a CA, a principals file and remote KMP and MADE before a first session, and the only SDK is the Go library (8). 20+20+16+19+8 = 83.

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.

AXLR 55

Apache-2.0 with a NOTICE (30). No privacy policy or terms on underpassai.com or axlr.underpassai.com; the docs' 'Where data goes' and 'Diagnostics and privacy' sections say that model requests go to OpenRouter, the local server or the native API, that Jev sends text to TypeSafe only when on, that sessions live under $XDG_STATE_HOME/axlr, that payload capture is off by default and redacted when on, and that traces are deleted after 30 days; nothing covers the engine downloads' or the catalog registry's handling of a client's requests (15). No deprecation policy; pre-1.0 changes are dated inline in the docs and the product contract records the 5 October 2026 retirement of the first skill catalogue after the fact (6). No telemetry to disclose, and the docs say in two places what leaves the machine and how to stop payload capture, though no single page says there is no telemetry (17). 30+15+6+17 = 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.

AXLR 62

Harness reading of the framework checklist, as for the other four harnesses. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. No product telemetry in the console source (the outbound hosts are openrouter.ai, api.anthropic.com, api.openai.com, a configured local server, api.github.com and github.com for engine downloads, and registry.underpassai.com for the signed catalog index) or in the docs; payload capture is off by default since 9 October 2026, traces omit prompts and credentials, model keys are never given to commands or plugins, and Jev sends requests and answers to TypeSafe only when on, which the setup assistant does when TYPESAFE_API_KEY is set, with a notice on stderr (27). Approval cards, a destructive list that always asks, four work modes, a policy level per execution, a bubblewrap or container sandbox with an enforced egress allow list, and a service that approves nothing but reads. Against that, the setup assistant writes autonomous: true, exec_sandbox is off by default, forged tools run with the person's rights, and the README says the console and worker are not sandboxes (13). Forged tools are refused when a file changes since the forge, a policy forbids calls outside the model, and the docs say MCP tools keep their own side effects, but no prompt-injection guidance was found and MCP results reach the model unmarked (6). The service keeps an event journal, audit records, a receipt with the SHA-256 of every call's arguments and outcome, and correlation ids on every event; the console keeps session records, a redacted app log and /session (14). No SECURITY.md, no security.txt on either host, no advisories, no bug bounty; release checksums and a minisign-signed catalog are integrity, not a programme (2). 27+13+6+14+2 = 62.

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.

AXLR 80

An OpenAPI 3.1 file for the service (15 paths, 23 schemas, mutualTLS security scheme, additionalProperties: false on request bodies), a checked proto for the gRPC service, and the 19 MCP tools built from the same shared schemas (25). No llms.txt on either site (404), and the docs site renders HTML; the Markdown sources are in the repository (5). The product contract tables what each of the four interfaces can and cannot do, the work-mode table states each mode's purpose and tool policy, the transport parity ledger names every verb's arguments and behaviour, and axlr_tools tells the model to look for a tool before forging one (15). Typed inputs throughout, Idempotency-Key 16 to 128 safe ASCII characters, expected_revision a positive integer, policy levels, sandbox profiles and egress values enumerated, budgets as four integers, and the service rejects unknown fields, invalid types and bodies over 4 MiB (14). Examples in every guide, an error shape of code, message and request_id, named codes (409 idempotency_conflict, 400 invalid_cursor, 422 invalid_policy, invalid_budget, sandbox_unavailable, not_ready, invalid_id), a gRPC status mapping, and the worker's five statuses and three exit codes; no single error reference page (14). /v1 routes and an OpenAPI version of 0.1.0 against a 0.15.0 release, and no changelog beyond the dated notes inside the docs (7). 25+5+15+14+14+7 = 80.

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.