T3 Code vs Warp (Warp Agent CLI and the Oz Agent API)

T3 Code 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.

T3 Code 55

Harness reading. User docs in the repository (managed policy, handoffs, providers, telemetry), AGENTS.md for contributors, a server other clients connect to (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.

T3 Code 51

MIT (30). docs/user/telemetry.md lists what is sent and what isn't, but includes hashed third-party account identifiers and the README doesn't mention it (15 of 30). No deprecation policy (5). Disclosed with an opt-out, on by default (12 of 20). 30 + 15 + 5 + 12 = 62.

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.

T3 Code 35

Harness reading. Product usage events go by default to ingest.t3.codes and PostHog, with hashed identifiers for your T3 Connect, OpenAI and Claude accounts, and relay traces to Axiom, which can include machine names and error text. Off with T3CODE_TELEMETRY_ENABLED=false or a managed policy. Disclosed in docs/user/telemetry.md, not the README (10 of 30). Permission modes and managed policies (12 of 20). No prompt-injection guidance (5). No audit log (5). No security policy file found (3). 10 + 12 + 5 + 5 + 3 = 35.

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.

T3 Code 43

Local software. An install script and desktop and mobile apps from the vendor (20). ci.yml and windows-tests.yml run on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Stable tags v0.1.5 to v0.1.7 with many nightlies, no changelog file (8). Version 0.1.7 (0). 20 + 15 + 0 + 8 + 0 = 43.

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 21 workflow files on 4 November. Whether CI passes on the default branch could not be read (15). Issue and pull request counts from the 18 October check came through shields.io badges, a third-party copy of GitHub data this run bars, and are struck. The clone shows 613 commits to master from 6 August. 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. Per the 18 October check, not re-read on 4 November, 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. 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.

T3 Code 75

Commits and nightly tags on 6 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 official apps and install script (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.