# Agent Zero vs Traycer (slim)

> Traycer scores 57 (C) to Agent Zero's 46 (D) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/agent-zero-vs-traycer.md (~5,150 tokens) · this version ~1,630 tokens · JSON https://www.anchorterminal.com/compare/agent-zero-vs-traycer.json · canonical https://www.anchorterminal.com/compare/agent-zero-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 scores 57 (C) on agent readiness against Agent Zero's 46 (D), and leads in 3 of 7 scored categories. Agent Zero leads on security & auth and payments & pricing. Both do agent harnesses.

- Agent Zero: D 46, rank #1168 of 1486 · https://www.anchorterminal.com/tools/agent-zero.min.md
- Traycer: C 57, rank #811 of 1486 · https://www.anchorterminal.com/tools/traycer.min.md
- Agent Zero, good for A technical owner who wants an agent with its own Linux machine, reachable from Telegram, WhatsApp or email, with scheduled tasks and editable memory. Ahead on Security & auth, 54 against 42; Payments & pricing, 60 against 30.
- Traycer, good for Teams who want several coding agents working together with shared context and boards. Ahead on Reliability, 65 against 57. Also No incidents deducted, where Agent Zero loses 15 points for them.

| Category | Agent Zero | Traycer |
| --- | --- | --- |
| Reliability (16%) | 57 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 64 | 65 |
| Agent ergonomics (13%) | 62 | 65 |
| Security & auth (14%) | 54 | 42 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 75 |
| Transparency & trust (7%) | 64 | 60 |

| Fact (where they differ) | Agent Zero | Traycer |
| --- | --- | --- |
| Vendor | Agent Zero, s.r.o. | Traycer AI |
| llms.txt | yes | no |
| Last release | 2026-11-01 | 2026-11-06 |
| Popularity | 19k stars | none |

Why the edge:
- Payments & pricing, Agent Zero +30: Agent Zero 60 (Read with the self-hosted rule. No payment protocol in the source (0). Free under MIT with nothing to buy for the software, so 20, 20 and 20 on the last three lines. It starts with one Docker command and no account. Model usage is billed by whichever provider the owner configures, or costs nothing with a local model. The vendor's site also describes a beta LLM API whose daily quota depends on staking its A0T token. That is separate from the software and not scored.); 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.)
- Security & auth, Agent Zero +12: Agent Zero 54 (Harness reading of the framework checklist, the one the Goose calibration dossier uses. 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 usage telemetry was found in the source. An update check, on by default, posts the version and a 20-character SHA-256 hash of a random per-install id to api.agent-zero.ai. The Update Checker settings page says only that ID and the version are sent and has an off switch. Something still leaves the machine by default, so the partial is kept (22). The agent works inside a Docker container built on Kali Linux and runs as root there. Tool Access can block tools by project or profile and defaults to allow, host access through the A0 CLI is scoped by read, write and execute permissions, and no approval step was found before a shell command, a file deletion or an outgoing message. The web interface has no login until a username is set (10). Infection Check audits the agent's reasoning with a second model before each tool call and ships disabled. Scanners check plugins, skills and MCP servers before install. The channel allow-lists accept every sender when empty, and the email filter matches the claimed From address only, which the plugin README states (7). Chat logs, visible tool steps and Time Travel snapshots, with no per-call audit log. Per-process log files were removed in v2.5 (9). No SECURITY.md on 4 November, security.txt answered 404 on 12 October, and none of the eight CVEs published from 17 March to 22 October 2026 came from the vendor (VulDB, VulnCheck, MITRE and CISA assigned them). A security-review ledger in the repository records two findings, and the v2.12 notes name both fixes (6, a partial kept).); 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 +8: Agent Zero 57 (Read with the local-software lines, as software the owner runs. Installs from the `agent0ai/agent-zero` Docker image, an install script, or a desktop Launcher with builds for macOS, Linux and Windows on x86 and ARM64. The README says it runs wherever Docker runs. The image registry page was not read (17 of 20). The repository holds 245 files under tests/ on 4 November, and its only two workflows still publish Docker images and close inactive issues. The publish workflow runs no tests, so no public CI run shows them passing (5 of 25, a partial kept). 139 open issues and pull requests on 12 October 2026, per that check (GitHub's pages and API weren't read on 4 November). Open reports from September include a crash of `run_ui` after a failed memory consolidation (#1909), a browser worker that hangs the agent turn (#1923) and truncated backups (#1904), each with no reply or one, and a workflow closes anything inactive for 90 days (11 of 25). Release notes for v2.11, v2.12 and v2.13 carry a Breaking Changes section, but breaking changes ship in minor versions, so the numbering is not semver (9 of 15). v2.15, past 1.0 (15).); 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.)