# Prime Agent vs Traycer (slim)

> Traycer and Prime Agent score within a point of each other for agent harnesses, 57 and 56.8 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

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

Traycer and Prime Agent score within a point of each other on agent readiness, 57 (C) and 56.8 (C). Prime Agent leads on agent ergonomics, security & auth, payments & pricing and transparency & trust. Both do agent harnesses.

- Prime Agent: C 56.8, rank #815 of 1486 · https://www.anchorterminal.com/tools/prime-agent.min.md
- Traycer: C 57, rank #811 of 1486 · https://www.anchorterminal.com/tools/traycer.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 Agent ergonomics, 73 against 65; Security & auth, 50 against 42; Payments & pricing, 60 against 30; Transparency & trust, 67 against 60. Also Free to start without a card.
- Traycer, good for Teams who want several coding agents working together with shared context and boards. Ahead on Reliability, 65 against 58; Schema & documentation, 65 against 45. Also No incidents deducted, where Prime Agent loses 3 points for them.

| Category | Prime Agent | Traycer |
| --- | --- | --- |
| Reliability (16%) | 58 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 45 | 65 |
| Agent ergonomics (13%) | 73 | 65 |
| Security & auth (14%) | 50 | 42 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 79 | 75 |
| Transparency & trust (7%) | 67 | 60 |

| Fact (where they differ) | Prime Agent | Traycer |
| --- | --- | --- |
| Vendor | Prime Intellect | Traycer AI |
| 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:
- Payments & pricing, Prime Agent +30: Prime Agent 60 (Self-hosted rule. No payment protocol (0). Free and MIT-licensed with nothing to buy, so 20, 20 and 20 on the last three lines. The model provider is paid separately.); Traycer 30 (Scored on the paid option, Traycer's own inference subscription, whose price wasn't read (0 of 20). No protocol (0). Bring-your-own-agent use is free (20). Accounts for sync and teams weren't checked, half (10). 0 + 0 + 20 + 10 = 30.)
- Schema & documentation, Traycer +20: 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.); Traycer 65 (Harness reading. Mintlify docs, a protocol package and a CLI (65).)
- Agent ergonomics, Prime Agent +8: 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).); Traycer 65 (Harness reading. Model switching within an agent, agent-to-agent loops, a CLI and cross-device sync (65).)
- Security & auth, Prime Agent +8: 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.); Traycer 42 (Harness reading. Code is processed in memory and not used for training, but Privacy Mode is opt-in for individuals, prompts may be logged with it off, and Sentry and PostHog 'may be enabled in release builds' (10 of 30). No approval model described in the README (8 of 20). No prompt-injection guidance (5). No audit log found (5). SECURITY.md, CodeQL, Scorecard and secret scanning (14 of 20). 10 + 8 + 5 + 5 + 14 = 42.)
- Reliability, Traycer +7: 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.); Traycer 65 (Local software. Builds for macOS, Linux and Windows, and package-manager publishing workflows (20). test.yml, CodeQL, OpenSSF Scorecard and secret scanning 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). CHANGELOG.md (15). Host 1.5.3 (15). 20 + 15 + 0 + 15 + 15 = 65.)
- Transparency & trust, Prime Agent +7: 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.); Traycer 60 (MIT (30). README privacy section and a linked privacy policy (not read) (18 of 30). CHANGELOG.md, no deprecation policy (10). Analytics described as 'may be enabled', with no opt-out given in the README (8 of 20). 30 + 18 + 10 + 8 = 66.)