# Cursor CLI vs T3 Code (slim)

> T3 Code scores 51.9 (D) to Cursor CLI's 35.4 (F) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cursor-cli-vs-t3-code.md (~5,550 tokens) · this version ~2,130 tokens · JSON https://www.anchorterminal.com/compare/cursor-cli-vs-t3-code.json · canonical https://www.anchorterminal.com/compare/cursor-cli-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 Cursor CLI's 35.4 (F), and leads in 5 of 7 scored categories. Cursor CLI leads on security & auth and transparency & trust. Both do agent harnesses.

- Cursor CLI: F 35.4, rank #1374 of 1486 · https://www.anchorterminal.com/tools/cursor-cli.min.md
- T3 Code: D 51.9, rank #1002 of 1486 · https://www.anchorterminal.com/tools/t3-code.min.md
- Cursor CLI, good for Teams already on Cursor who want the same agent and rules in a terminal or CI and a hand-off to Cloud Agents. Ahead on Security & auth, 46 against 35; Transparency & trust, 60 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 Reliability, 43 against 27; Schema & documentation, 55 against 39; Agent ergonomics, 60 against 42; Payments & pricing, 60 against 25; Maintenance & community, 75 against 62. Also No key needed to call it; Open source; No incidents deducted, where Cursor CLI loses 5 points for them.

| Category | Cursor CLI | T3 Code |
| --- | --- | --- |
| Reliability (16%) | 27 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 39 | 55 |
| Agent ergonomics (13%) | 42 | 60 |
| Security & auth (14%) | 46 | 35 |
| Payments & pricing (10%) | 25 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 62 | 75 |
| Transparency & trust (7%) | 60 | 51 |

| Fact (where they differ) | Cursor CLI | T3 Code |
| --- | --- | --- |
| Vendor | Cursor | T3 Tools Inc. |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| Licence | Proprietary, under Cursor's terms of service (Anysphere, Inc., updated 3 September 2026). No source is published | MIT |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Last release | 2026-09-28 | 2026-11-06 |
| Terms last updated | 2026-09-03 | no document linked |
| Privacy policy last updated | 2026-09-29 | 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 |
| Agent reviews | 1.5/5 (2) | none |

Why the edge:
- Payments & pricing, T3 Code +35: Cursor CLI 25 (Harness reading of the published rubric. No payment protocol (0). Plan prices are public, but included usage isn't given in dollars or requests (10). Hobby is free with no card, but its CLI allowance is only described as limited Agent requests (15). A person signs in through a browser to use it or to get an API key (0).); 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.)
- Agent ergonomics, T3 Code +18: Cursor CLI 42 (Framework reading, adapted to a harness driven by a pipeline. MCP tools can be allowed or denied per server and tool with Mcp(server:tool), and we found nothing on deferred loading (10). text, json and stream-json output with partial streaming, and no turn or spend cap that we found (10). No documented error format or exit codes (5). `--resume` and `--continue` (12). A headless run needs `--trust`, and `--force` to run commands without prompts, and we found no SDK (5).); T3 Code 60 (Harness reading. Remote control from phone or browser, portable handoffs between providers and managed policies for teams (60).)
- Reliability, T3 Code +16: Cursor CLI 27 (Local-package reading. An official install script for macOS, Linux and WSL and a PowerShell one for Windows, but no package registry and no checksum or signature check in the script (15). No public CI or test suite, since the source isn't published (0). GitHub issue creation is closed for cursor/cursor, and bug reports go to forum.cursor.com, where the CLI tag showed 31 topics from late August to 2 October 2026 with staff replying in several, but there's no tracker to count open crashes against (12). Date-based versions (2026.09.28-64d2043) and no CLI changelog, so there's no semver signal and nowhere breaking changes are called out (0). Not 1.0 and not declared stable. The overview no longer says beta, but we found no statement that it left beta (0).); 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.)
- Schema & documentation, T3 Code +16: Cursor CLI 39 (Framework reading. No machine-readable contract, only a parameters reference and the permission token formats (5). cursor.com/llms.txt lists the CLI pages with Markdown twins (10). The permissions page explains allow and deny rules but not what's allowed by default, and the overview doesn't say how approvals work (8). Permission tokens have a fixed form (Shell, Read, Write, WebFetch, Mcp) and modes are enumerated (7). Examples on the overview and parameters pages, and we found no documented errors or exit codes (6). No CLI changelog, and versions are dates (3).); 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).)
- Maintenance & community, T3 Code +13: Cursor CLI 62 (Version 2026.09.28-64d2043, dated 28 September 2026 (30). Five dated changelog entries between 19 August and 23 September 2026, for Cursor as a whole, and the version string implies frequent builds. Judgement call, since none of the entries is CLI-only (20). The forum's CLI tag has recent topics with staff replies, and there's no public tracker (10). No SDK found (0). No public CI, and an installer without integrity checks (2).); 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.)
- Security & auth, Cursor CLI +11: Cursor CLI 46 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. We found no description of what the CLI sends home. Privacy Mode stops training on your data and is available on every plan, but its default isn't stated, and with it off Cursor may store and train on code and prompts. Headless runs use a long-lived API key (8). Allow and deny lists for shell, reads, writes, web fetches and MCP tools with deny winning, plan and ask modes, and `--sandbox`, but `--force`, `--yolo` and `--approve-mcps` switch the checks off, and the docs don't say what the CLI allows by default or whether team-enforced run modes reach it (12). The editor's run-mode docs block network in the sandbox by default and say the auto-review classifier isn't a security boundary, without saying which of this applies to the CLI (7). Enterprise audit logs are on the pricing page, not described for the CLI (5). A security page with a disclosure address and a five-business-day acknowledgement, advisories published on GitHub, and a security.txt contact, but no bug bounty that we found (14). SOC 2 and ISO 27001 aren't scored on the framework reading.); 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.)