# Agent Zero vs T3 Code (slim)

> T3 Code scores 51.9 (D) 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-t3-code.md (~5,650 tokens) · this version ~2,130 tokens · JSON https://www.anchorterminal.com/compare/agent-zero-vs-t3-code.json · canonical https://www.anchorterminal.com/compare/agent-zero-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)

T3 Code scores 51.9 (D) on agent readiness against Agent Zero's 46 (D), and leads in 0 of 7 scored categories. Agent Zero leads on reliability, schema & documentation, security & auth and transparency & trust. Both do agent harnesses.

- Agent Zero: D 46, rank #1168 of 1486 · https://www.anchorterminal.com/tools/agent-zero.min.md
- T3 Code: D 51.9, rank #1002 of 1486 · https://www.anchorterminal.com/tools/t3-code.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 Reliability, 57 against 43; Schema & documentation, 64 against 55; Security & auth, 54 against 35; Transparency & trust, 64 against 51.
- T3 Code, good for Developers who want one app, including on their phone, to drive several coding agents they already pay for. Also No incidents deducted, where Agent Zero loses 15 points for them.

| Category | Agent Zero | T3 Code |
| --- | --- | --- |
| Reliability (16%) | 57 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 64 | 55 |
| Agent ergonomics (13%) | 62 | 60 |
| Security & auth (14%) | 54 | 35 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 75 |
| Transparency & trust (7%) | 64 | 51 |

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

Why the edge:
- Security & auth, Agent Zero +19: 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).); 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.)
- Reliability, Agent Zero +14: 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).); 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.)
- Transparency & trust, Agent Zero +13: Agent Zero 64 (MIT, copyright Agent Zero, s.r.o. (30). No privacy policy for the software was found. The site's cookie notice covers the website, and its terms (14 May 2026) cover the community platform. The docs say where data lives (chats, memory, secrets and settings under `/a0/usr`) and warn that model providers see what is sent to them only in general terms, with no retention statement (8 of 30). Release notes list breaking changes and removals with the release date, and one deprecated alias is named. No deprecation policy or notice period was found (8 of 20, a partial kept). No usage telemetry was found in the source. The update check is described on its settings page, which says it sends only a randomised, hashed install ID and the version number, and the same page turns it off. The ID is a hash of a random per-install token, a pseudonym under this run's reading, so the statement holds (20). 30 + 8 + 8 + 20 = 66.); 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.)
- Schema & documentation, Agent Zero +9: Agent Zero 64 (Harness reading of the lines, as the Goose calibration dossier does. No OpenAPI file. The connectivity page lists five external endpoints and the `X-API-KEY` header, then sends readers to the source or DeepWiki for request and response details. Each API handler and tool has a `.dox.md` contract file in the repository, and the MCP client JSON shape is documented (10 of 25). llms.txt at www.agent-zero.ai, and AGENTS.md contract files across the repository (10). Guides say which path to use for a need, with tables that separate the browser, the host connector, MCP and A2A (14 of 20). The v2.12 notes say 15 bundled tools gained argument descriptions in non-strict schemas, and plugin settings are typed YAML with commented examples (8 of 15). Guides carry worked examples and a troubleshooting page, with no documented error responses for the external API (9 of 15). Dated notes on every GitHub release and a release article for each version on the site, with no version prefix on API routes (13 of 15).); 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).)