# Qoder CLI vs Verdent (slim)

> Qoder CLI scores 59.5 (C) to Verdent's 39.7 (E) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/qoder-cli-vs-verdent.md (~6,950 tokens) · this version ~3,330 tokens · JSON https://www.anchorterminal.com/compare/qoder-cli-vs-verdent.json · canonical https://www.anchorterminal.com/compare/qoder-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)

Qoder CLI scores 59.5 (C) on agent readiness against Verdent's 39.7 (E), and leads in every scored category. Both do agent harnesses.

- Qoder CLI: C 59.5, rank #695 of 1486 · https://www.anchorterminal.com/tools/qoder-cli.min.md
- Verdent: E 39.7, rank #1317 of 1486 · https://www.anchorterminal.com/tools/verdent.min.md
- Qoder CLI, good for Developers already on Qoder who want the same agent in a terminal, in CI through a PAT, in Zed through ACP, or embedded through the Agent SDK. Ahead on Reliability, 51 against 43; Schema & documentation, 81 against 55; Agent ergonomics, 80 against 35; Security & auth, 58 against 33; Payments & pricing, 35 against 20; Maintenance & community, 72 against 61; Transparency & trust, 61 against 55.
- 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.

| Category | Qoder CLI | Verdent |
| --- | --- | --- |
| Reliability (16%) | 51 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 55 |
| Agent ergonomics (13%) | 80 | 35 |
| Security & auth (14%) | 58 | 33 |
| Payments & pricing (10%) | 35 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 72 | 61 |
| Transparency & trust (7%) | 61 | 55 |

| Fact (where they differ) | Qoder CLI | Verdent |
| --- | --- | --- |
| Vendor | Qoder (BRIGHT ZENITH PRIVATE LIMITED) | Verdent AI, Inc. |
| Pricing | Freemium | Paid |
| Licence | Proprietary, under the Qoder Terms of Service (BRIGHT ZENITH PRIVATE LIMITED, last updated 29 April 2026). No source is published, and the Agent SDK's LICENSE file points to the same terms | Proprietary. The terms of use from Verdent AI, Inc. forbid reverse engineering or copying any component, and no source is published |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-10-16 | 2026-10-29 |
| Terms last updated | couldn't be read | 2026-05-25 |
| Privacy policy last updated | couldn't be read | 2026-05-26 |
| Customer content may train models | couldn't be read | yes |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 5k npm/wk | none |
| Agent reviews | 3.5/5 (4) | none |

Why the edge:
- Agent ergonomics, Qoder CLI +45: Qoder CLI 80 (Framework reading, adapted to a harness driven by a pipeline. `--tools`, `--allowed-tools` and `--disallowed-tools` restrict built-in tools, and `--strict-mcp-config` with `--allowed-mcp-server-names` limits MCP servers. Nothing on deferred MCP tool loading was found (18). text, json and stream-json output, `--max-turns`, `--max-output-tokens` and `--no-session-persistence` (16). Distinct exit codes for authentication, input, configuration, turn-limit and tool failures, and SDK Result subtypes with error codes (16). `--continue`, `--resume`, `--session-id`, `--fork-session`, SDK checkpoints with rewind, and `--max-model-request-retries` (15). Official SDKs in TypeScript and Python, an ACP server, and headless runs that need only a PAT and a permission flag (15). 18+16+16+15+15 = 80. Per the 18 October check, not re-read on 4 November (Qoder's terms bar scraping its Services by automated means, so its sites are paused for this run).); 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.)
- Schema & documentation, Qoder CLI +26: Qoder CLI 81 (Framework reading. A CLI reference with types and defaults for every flag, a settings reference with types and defaults, TypeScript declaration files and a Python reference for the SDK, and Result and error-code tables. No schema for the stream-json events was found (16). docs.qoder.com/llms.txt indexes every page with a Markdown twin, and robots.txt allows both (10). The permissions page states what each mode does and is best for, what headless runs do with ask, and which actions skip the auto classifier (17). Permission modes and output formats are enums and rules have a fixed syntax (12). CI examples, an SDK error page with exit codes 0, 1, 41, 42, 44, 52, 53, 54 and 130, Result subtypes and a troubleshooting index. Code 44 names a sandbox the docs don't describe (14). Dated release notes for the CLI and the SDK, though the SDK notes stop at 1.0.41 on 15 September while npm has 1.0.53, and the CLI reference still names the removed `lite` model (12). 16+10+17+12+14+12 = 81. Per the 18 October check, not re-read on 4 November (Qoder's terms bar scraping its Services by automated means, so its sites are paused for this run).); 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, Qoder CLI +25: Qoder CLI 58 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Browser sign-in with background refresh, or a PAT created with chosen permissions and an expiry and revocable, plus scoped service accounts for organisations. Usage statistics and AI code statistics are on by default with documented opt-outs, and the privacy policy lets users turn off Share & Improve depending on the plan, without saying which plans or the default (18). Five permission modes, deny over ask over allow across seven rule layers, ask turned into deny in headless runs, a `dont_ask` mode, trusted directories, protected paths and an administrator switch that disables YOLO. No local sandbox is documented, and `auto` mode lets an AI classifier decide and approves read-only tools on any path (14). Workspace files can't add auto-mode rules, protected paths stop the agent changing shell startup files or .mcp.json without approval, and network paths always ask on Windows. A project's .qoder/settings.json is still one of the rule layers, and nothing contains a command once approved (9). The enterprise audit log records administrative and configuration events for administrators and says it leaves out prompts, terminal commands, MCP call parameters and CLI execution, and individuals have local session history only (5). qoder.com/enterprise says Qoder is certified to ISO/IEC 27001 and has completed a SOC 2 Type II audit. No security.txt, disclosure policy or bug bounty was found, and fixes appear as one-line release notes without advisories. Graded 12 against the named comparables for ISO 27001 and SOC 2 claims with no disclosure route (fireworks-inference, people-data-labs, launchdarkly), where the 18 October check gave 9 (12). 18+14+9+5+12 = 58. Per the 18 October check, not re-read on 4 November (Qoder's terms bar scraping its Services by automated means, so its sites are paused for this run).); 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.)
- Payments & pricing, Qoder CLI +15: Qoder CLI 35 (Harness reading of the published rubric, scored on the Qoder subscription the CLI needs. No payment protocol (0). Plan prices, the Credit Pack price ($20 for 1,500 credits) and per-model credit factors are public in the docs without a login. qoder.com/pricing is disallowed by robots.txt and wasn't read (20). A Free plan with basic models for a limited number of messages and a 14-day Pro trial with 300 credits. We found no statement on whether a card is needed (15). A person signs in through a browser, and a PAT is created by hand at qoder.com/account/integrations (0). 0+20+15+0 = 35. Per the 18 October check, not re-read on 4 November (Qoder's terms bar scraping its Services by automated means, so its sites are paused for this run).); 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.)
- Maintenance & community, Qoder CLI +11: Qoder CLI 72 (1.1.73 on 16 October 2026, 19 days before 4 November (30). 74 dated CLI versions between 20 July and 16 October 2026, well over three of them after 6 August (20). No public issue tracker. A Discourse forum with bug-report and feature-request categories, where 15 of the 29 bug reports on the first page had no reply when read on 18 October (7). Current official SDKs, `@qoder-ai/qoder-agent-sdk` 1.0.53 on 15 October and `qoder-agent-sdk` 1.0.15 on PyPI on 23 September 2026 (12). No public CI. npm versions carry registry signatures and the install script checks a SHA-256 (3). 30+20+7+12+3 = 72. Per the 18 October check, not re-read on 4 November (Qoder's terms bar scraping its Services by automated means, so its sites are paused for this run). npm and PyPI were not reachable for newer versions.); Verdent 61 (Closed service. v2.18.0 on 29 October 2026, eight days before this check (30). More than three dated releases in the 90 days from 8 August, among them 2.10.0 to 2.18.0 (20). A dated public changelog, a support address, Discord and a subreddit, with no public tracker to read reply times (8). No official SDK or MCP server to keep current (0). No public packages or CI to judge (3). 30+20+8+0+3 = 61.)
- Reliability, Qoder CLI +8: Qoder CLI 51 (Local-package reading, the same as the other closed-source harnesses. An install script for macOS, Linux and Windows on arm64 and amd64 that checks a SHA-256 from a manifest on the same download host, and an npm package with Node.js 20 or later stated (20). No public CI or test suite, since no source is published (0). We found no public issue tracker for the CLI. The forum's bug-reports category, shared by every Qoder product, had 116 new topics in the month to 18 October, and 15 of the 29 topics on its first page had no reply. A few named the CLI (8). Versions are semver-shaped and every release is dated in the release notes, but removals such as `/goal take` in 1.1.11 shipped in patch versions without a breaking-change label (8). 1.0.0 on 20 May 2026, now 1.1.73 (15). 20+0+8+8+15 = 51. Per the 18 October check, not re-read on 4 November (Qoder's terms bar scraping its Services by automated means, so its sites are paused for this run).); 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.)