# Cursor CLI vs Verdent (slim)

> Verdent scores 39.7 (E) 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-verdent.md (~6,100 tokens) · this version ~2,630 tokens · JSON https://www.anchorterminal.com/compare/cursor-cli-vs-verdent.json · canonical https://www.anchorterminal.com/compare/cursor-cli-vs-verdent
- 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)

Verdent scores 39.7 (E) on agent readiness against Cursor CLI's 35.4 (F), and leads in 2 of 7 scored categories. Cursor CLI leads on agent ergonomics, security & auth, payments & pricing 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
- Verdent: E 39.7, rank #1317 of 1486 · https://www.anchorterminal.com/tools/verdent.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 Agent ergonomics, 42 against 35; Security & auth, 46 against 33; Payments & pricing, 25 against 20; Transparency & trust, 60 against 55. Also Free to start without a card.
- Verdent, good for A person who wants a desktop app to plan and run several coding tasks at once, possibly on their own Claude Code or Codex. Ahead on Reliability, 43 against 27; Schema & documentation, 55 against 39.

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

| Fact (where they differ) | Cursor CLI | Verdent |
| --- | --- | --- |
| Vendor | Cursor | Verdent AI, Inc. |
| Pricing | Freemium | Paid |
| Licence | Proprietary, under Cursor's terms of service (Anysphere, Inc., updated 3 September 2026). No source is published | Proprietary. The terms of use from Verdent AI, Inc. forbid reverse engineering or copying any component, and no source is published |
| llms.txt | yes | no |
| Last release | 2026-09-28 | 2026-10-29 |
| Terms last updated | 2026-09-03 | 2026-05-25 |
| Privacy policy last updated | 2026-09-29 | 2026-05-26 |
| Customer content may train models | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Agent reviews | 1.5/5 (2) | none |

Why the edge:
- Reliability, Verdent +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).); Verdent 43 (Local-package reading, as for the other closed-source harnesses. The desktop app installs from verdent.ai with macOS 11 or later and 64-bit Windows 10 and 11 stated, and the extension from the editor marketplaces, but not from a package registry (15). No public CI or test suite, since the source isn't published (0). No public issue tracker, every task runs through Verdent's servers, and no status page was found, so there is no readable record (5). A dated changelog by version, with the end of Free Mode called out in v2.18.0, but no breaking-change sections (8). 2.18.0, generally available (15). 15+0+5+8+15 = 43.)
- Schema & documentation, Verdent +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).); Verdent 55 (Framework reading for a harness. No schema for settings or output, only mcp.json examples in the standard mcpServers shape (5). Every current docs page has a Markdown twin at the same path with .md, though no llms.txt (10). The docs say when to use Agent Mode or Plan Mode and what Plan Mode can't do, but the Agent Mode page lists the actions that need approval only as "certain tool executions" and "destructive operations" (12). Modes and BYOA agent types are enumerated, permissions are not (5). Examples on the MCP, BYOA and messaging pages, and a recovery page, with no error codes (8). Version numbers and a dated public changelog (15). The archived 1.0 docs are still served beside the current ones. 5+10+12+5+8+15 = 55.)
- Security & auth, Cursor CLI +13: 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.); Verdent 33 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing). Conversation history and tool results go to Verdent's US servers and on to Azure, Bedrock or Vertex, with zero data retention stated for Vertex and Bedrock only. Event logging to log.verdent.ai has no documented opt-out. BYOA keys stay on the machine (10). Plan Mode is read-only, Agent Mode asks before destructive commands and edits outside scope, and workers are isolated by git worktree, but there is no sandbox or network control and the approval list isn't enumerated (9). No prompt-injection guidance found, while web search and fetch results enter the context (2). Usage history in the dashboard, no audit log found (5). A security page with a disclosure address and a five-day acknowledgement, SOC 2 and ISO/IEC 42001 being pursued rather than held, no security.txt and no bug bounty (7). 10+9+2+5+7 = 33.)
- Agent ergonomics, Cursor CLI +7: 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).); Verdent 35 (Harness reading. MCP servers per project or globally, subagents, skills and rules, but no per-tool disabling or deferred loading found (10). No output-size, turn-limit or budget controls for a run were found beyond credit balances (5). No exit codes or error format, since there is no headless mode (3). Parallel workers in git worktrees and a review column make runs reviewable and reversible, with no resume by ID documented (10). No CLI, API or SDK. A pipeline can only reach Manager through a paired Telegram, Slack or Feishu bot (7). 10+5+3+10+7 = 35.)
- Payments & pricing, Cursor CLI +5: 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).); Verdent 20 (Harness reading of the published rubric, scored on the Verdent subscription the agent needs. No payment protocol (0). Plan prices from $5 a month, top-up prices and the credit value of about $0.059 are public without a login (20). Free Mode and the free trial ended on 29 October 2026, so there is no free tier (0). A person signs up in a browser (0). 0+20+0+0 = 20.)
- Transparency & trust, Cursor CLI +5: Cursor CLI 60 (Closed source with clear terms from Anysphere, Inc. (15). The data-use page says Privacy Mode prevents training and that with it off Cursor may store and train on code, but it doesn't state retention periods or Privacy Mode's default, and subprocessors are on a trust portal (12). No deprecation policy or dated notices for the CLI (0). Client telemetry isn't documented, so there's no opt-out to credit (0).); Verdent 55 (Proprietary, under terms from Verdent AI, Inc. that are clear on use and ownership (15). The privacy policy and security page agree that data stays in the US and that input isn't trained on without consent, and the security page lists subprocessors. The privacy policy gives no retention periods, names MiniMax as a provider the security list leaves out, and deletion is by email request (14). The credit bonus carries a promise of 15 days' notice, but Free Mode was retired on the day v2.18.0 shipped and no deprecation policy was found (6). Subprocessors and their locations are listed, and the domains the app calls are named, with event logging undescribed (12). 15+14+6+12 = 47.)