# Prime Agent vs T3 Code (slim)

> Prime Agent scores 56.8 (C) to T3 Code's 51.9 (D) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/prime-agent-vs-t3-code.md (~6,000 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/prime-agent-vs-t3-code.json · canonical https://www.anchorterminal.com/compare/prime-agent-vs-t3-code
- 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)

Prime Agent scores 56.8 (C) on agent readiness against T3 Code's 51.9 (D), and leads in 5 of 7 scored categories. T3 Code leads on schema & documentation. Both do agent harnesses.

- Prime Agent: C 56.8, rank #815 of 1486 · https://www.anchorterminal.com/tools/prime-agent.min.md
- T3 Code: D 51.9, rank #1002 of 1486 · https://www.anchorterminal.com/tools/t3-code.min.md
- Prime Agent, good for Long-running research and coding work where one model drives subagents, schedules and goals from code, and where the owner can isolate the machine. Ahead on Reliability, 58 against 43; Agent ergonomics, 73 against 60; Security & auth, 50 against 35; Transparency & trust, 67 against 51. Also Free to start without a card.
- T3 Code, good for Developers who want one app, including on their phone, to drive several coding agents they already pay for. Ahead on Schema & documentation, 55 against 45. Also No incidents deducted, where Prime Agent loses 3 points for them.

| Category | Prime Agent | T3 Code |
| --- | --- | --- |
| Reliability (16%) | 58 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 45 | 55 |
| Agent ergonomics (13%) | 73 | 60 |
| Security & auth (14%) | 50 | 35 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 79 | 75 |
| Transparency & trust (7%) | 67 | 51 |

| Fact (where they differ) | Prime Agent | T3 Code |
| --- | --- | --- |
| Vendor | Prime Intellect | T3 Tools Inc. |
| Last release | 2026-10-28 | 2026-11-06 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | no date given | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 22k stars | none |
| Agent reviews | 2.8/5 (4) | none |

Why the edge:
- Transparency & trust, Prime Agent +16: Prime Agent 67 (MIT in the LICENSE file and Cargo.toml, with a notice that the code is a port of a TypeScript product originally copyright Mario Zechner (30). The first-run notice and the telemetry crate README say what is sent and what is excluded, and name the endpoint and PostHog, but the vendor privacy policy, re-read on 3 November 2026, is still dated 23 February 2024, does not describe agent telemetry and gives no retention period for it (12). No deprecation policy found. Removed flags are recorded in change fragments and, since 0.10.1, in CHANGELOG.md (5). Telemetry is disclosed with a setting, a command and two environment variables to turn it off (20). 30 + 12 + 5 + 20 = 67.); 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.)
- Reliability, Prime Agent +15: Prime Agent 58 (Read with the local-software lines. The installer's stable channel now points at v0.10.2 (28 October 2026), the Rust build, with checksummed binaries for macOS and Linux on x64 and arm64 and for Windows x64, read from the channel manifest on 3 November 2026 (20). A public CI workflow runs fmt, clippy with warnings as errors, sharded workspace tests and cargo-deny on main. Its badge read passing on 8 October, but GitHub's pages answered 403 on 3 November, so the current pass state is unread (15). 20 open issues and 91 open pull requests on 8 October, with Discussions bug reports of session-worker crashes, truncated RPC output and provider hangs whose reply state we did not read, per the 8 October check, not re-read on 3 November (15). A dated CHANGELOG.md now covers 0.10.1 (21 October) and 0.10.2 (28 October), and 0.10.1 records the removal of the `--tools` flags, but no entry is marked breaking, 0.10.0 (9 October) has no entry and the project is at 0.x (8). Version 0.10.2, pre-1.0 (0). 20 + 15 + 15 + 8 + 0 = 58.); 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.)
- Security & auth, Prime Agent +15: Prime Agent 50 (Harness reading of the framework checklist, as used for the other 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. Usage telemetry is on by default. It is pseudonymous, limited to primitive values with no prompts, tool content or file paths per the source, disclosed on first run and mirrored to a local `telemetry.jsonl` (18). No approval prompts were found and there is no sandbox, which the README states. MCP tools can be limited with `enabledTools` and `disabledTools`, and the agent is told to recommend a connection, not make one (4). The README tells users to work only with trusted repositories, instructions and skills. No detection or mitigation found (5). Append-only JSONL session files, a `prime-agent incident` timeline command and the local telemetry mirror (12). The vendor's security policy has a reporting address, safe harbour, response times and discretionary rewards, scoped to its website and API. The repository has no SECURITY.md and no published advisories, CONTRIBUTING.md says to report privately without naming an address, and security.txt returned 404. security.txt still returned 404 on 3 November 2026 and the policy page (updated 6 May 2026) is unchanged. Fixes to the agent's own flaws ship in releases with no advisory (see negative). cargo-deny runs in CI (11). 18 + 4 + 5 + 12 + 11 = 50.); 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.)
- Agent ergonomics, Prime Agent +13: Prime Agent 73 (Harness reading, scored on what a person or pipeline driving it has to supply. The model sees three tools (bash, edit, ipython), and MCP tools are searched, described and called from Python instead of being loaded into the prompt (23). Autonomous mode has limits for turns, tokens, time and continuations, a goal token budget and automatic compaction (17). A JSON event stream and exit codes for headless runs, described in the crate README and source only (10). Sessions resume, the daemon restarts workers and restores from JSONL files, refinements can be rolled back and quality gates retry (15). One command starts it and no SDK was found. A provider must be chosen through an interactive `/login` or supplied as a key first (8).); T3 Code 60 (Harness reading. Remote control from phone or browser, portable handoffs between providers and managed policies for teams (60).)
- Schema & documentation, T3 Code +10: Prime Agent 45 (Harness reading of the framework line. `--mode json` emits a session event stream and `rpc` and `acp` modes exist, but we found no published schema or reference for them outside the source (10). docs.primeintellect.ai serves an llms.txt that still had no Prime Agent page on 3 November 2026 (0). The README states what the agent does, how it differs and that it is not a sandbox, and the bundled skills say when to use each function (10). CLI values are validated with messages that list the valid choices, and MCP tool schemas are read live from the server (7). The README gives the install line and the main commands, the repository's docs folder adds Slack and Google Workspace MCP connector guides, and the MCP skill documents its error types, but there is no headless or configuration guide (5). Versioned stable releases and, since 0.10.1 on 21 October 2026, a dated CHANGELOG.md in the repository. 0.10.0 has no entry and the nightly betas have none of substance (13). 10 + 0 + 10 + 7 + 5 + 13 = 45.); 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).)