Claude Code vs Verdent

Claude Code 91

Framework reading, adapted to a harness driven by a pipeline. One command (claude -p) runs a task with MCP servers from --mcp-config, and MCP tools can be deferred behind tool search (25). --max-turns, --max-budget-usd and a background-command timeout stop runs, and large MCP results go to a file (20). json and stream-json output, -p errors name the cause, and since 2.1.318 -p JSON results carry credential_expires_at and a timed-out claude.ai login names claude auth login and claude setup-token (16). --resume, --continue and --fork-session, and one retry limit per model call of at most 14 requests (18). Python and TypeScript Agent SDKs. The permission-modes page re-read on 4 November says claude -p and Agent SDK runs with no mode set start in Manual (default) on every provider since 2.1.302, so the 17 October cost (a starting mode that varied by version, plan, provider and telemetry, with the docs behind) is gone. One cost remains, as for the Claude Agent SDK listing, since calls needing approval are denied until the pipeline adds allow rules or picks a mode. Judgement call. Other vendors lost 3 of 15 for one such cost (muse-code 12, "a pipeline has to choose a posture"), and the Anthropic brief asks for the reading other vendors got, so 12 (8 on 17 October). Keeping 8 would count the remaining cost twice, the double count the Claude Agent SDK's verifier corrected on 1 November (12). 25 + 20 + 16 + 18 + 12 = 91.

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.

Claude Code 80

Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. The data-usage page, re-read on 4 November, says usage metrics are on by default on the Claude API without code, prompts or file paths, error reports are on by default for Pro, Max and Ultra sign-ins since v2.1.198, /feedback reports are on, session quality surveys run on every provider, and every provider sends WebFetch hostnames to api.anthropic.com for a blocklist check, each with an opt-out. Metrics, error reports and /feedback are off by default on Bedrock, Google Cloud, Foundry and Claude Platform on AWS unless a host sets CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST (18). Six modes, allow, ask and deny rules, protected paths, and managed settings that can disable bypass and auto mode. 2.1.314 added permissions.blockWritesOutsideWorkingDirectories. The sandbox is opt-in and absent on native Windows, and auto mode, a classifier rather than a person, is the built-in starting mode for terminal and VS Code sessions on 2.1.283 or later, per the permission-modes page re-read on 4 November; sandboxing per 17 October (16). The auto-mode classifier blocks named exfiltration patterns, the sandbox proxy denies hosts outside an allowlist that starts empty, and WebFetch checks a blocklist, but since 1 October 2026 a mod can approve a call a deny rule refuses unless managed settings or a Team or Enterprise sign-in hold it (11). Opt-in OpenTelemetry with tool content behind OTEL_LOG_TOOL_CONTENT, local transcripts for 30 days, and cloud sessions logged through a proxy; 2.1.317 adds plan, seat type and provider attributes (15). HackerOne bug bounty and SECURITY.md (unchanged since 15 May 2026 in the clone), advisories published with GHSA ids, the newest in GitHub's reviewed database GHSA-pq7j-f95f-qfcv (High, 15 October; OSV holds 29 for the package on 4 November, none newer), and anthropic.com's security.txt valid to 31 December 2026, re-read on 4 November (20). 18 + 16 + 11 + 15 + 20 = 80. SOC 2 isn't scored on the framework reading. Advisories and the changelog-only sandbox and permission fixes count under negative events. Judgement call, written by an agent on Claude, on the same checklist the other harnesses got.

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.

Claude Code 81

Closed source with clear terms, LICENSE.md pointing to the Commercial Terms, unchanged in the clone on 4 November (15). The data-usage page, re-read on 4 November, states retention per account type (consumer 30 days or 5 years with training on, commercial 30 days, zero retention for qualified Enterprise), 30 days of plaintext local transcripts, 5 years for /feedback reports and up to 6 months for shared survey transcripts, and these agree with the privacy policy links, but the logging and error-tracking services are named only as third parties. The page still doesn't say that since 2.1.300 local transcripts also record each API request's system prompt, tools and parameters, read as an omission rather than a contradiction (25). No written deprecation policy. The README still marks npm installs deprecated without a date. 2.1.316 gives Claude Code's first dated advance notice of its own, fast mode for Opus 4.8 deprecated on 30 October and removed on 30 November 2026, 31 days' notice. Judgement call. One dated notice and no policy; we kept 8, the stricter reading, and crediting the notice would give 10 and transparency 70 (8). Telemetry is documented per provider and per service with an opt-out for each, re-read on 4 November (20). 15 + 25 + 8 + 20 = 68.

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.

Claude Code 80

Framework reading. No published JSON Schema for settings that we checked (per the 1 October check, not re-read), but the settings reference types every key, and the stream-json output has typed message classes in the Python and TypeScript Agent SDKs (18). llms.txt at code.claude.com/docs/llms.txt with a Markdown version of each page; code.claude.com's robots.txt carries Content-Signal ai-train=yes, search=yes, ai-input=yes (10). The permission-mode table says what each mode is best for and, re-read on 4 November, now gives default as the starting mode for claude -p and the Agent SDK, matching 2.1.302. The rules still carry many version-specific exceptions (mods, protected paths, carve-outs by settings source) that a model has to read closely. Judgement call. The page catching up removes the reason given on 17 October but not the one given before it, so the line stays at 15 rather than rising; the lighter reading gives 17 and schema 82 (15). Permission modes, sandbox settings and rule syntax are enumerated, though rules are strings parsed at runtime (12). Examples on every page and a troubleshooting section for install and auth errors (13). A changelog for every release. CHANGELOG.md in the repository has no dates, feed.xml dates the latest 20 (2.1.318 at 00:00 UTC on 4 November), and the code.claude.com changelog page dated every release on 17 October. Breaking changes still aren't marked (12). 18 + 10 + 15 + 12 + 13 + 12 = 80.

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.

Claude Code 82

2.1.318 on 4 November 2026 (feed.xml 00:00:44 UTC, tag v2.1.318), not confirmed on npm because registry.npmjs.org didn't resolve and the fallback waited on an approval prompt (30). 81 release tags in the 90 days from 6 August (v2.1.223 on 6 August to v2.1.318), from the clone (20). A public issue tracker with automatic triage, duplicate detection and labels, but over 5,000 open issues and no visible maintainer replies on the page we read, per the 1 October check, not re-read since (12). The Python and TypeScript Agent SDKs that run the same loop are current, Python 0.2.176 and TypeScript 0.3.316 tagged 31 October, per the Claude Agent SDK listing's 1 November check (15). Signed releases and a stable channel, but no public CI for the program (5). 30 + 20 + 12 + 15 + 5 = 82.

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.

Claude Code 50

Local-package reading. Official installers for macOS 13+, Windows 10 1809+, Ubuntu 20.04+, Debian 10+ and Alpine 3.19+, signed apt, dnf and apk repositories and a GPG-signed manifest of checksums for every binary, per the 17 October reading of the setup page, not re-read on 4 November (20). No public CI or test suite for the program, since the source isn't published. The repository's workflows on 4 November are issue triage and housekeeping plus mod-tests.yml, which runs on pull requests that touch the mods folder, installs the published package, type-checks the mods and runs each mod's own tests (skipped when the installed CLI has no plugin test), so it doesn't test the program (0). Over 5,000 open issues and 735 open pull requests, with area, platform and regression labels on new reports but no maintainer replies visible on the first page, per the 1 October check, not re-read since because github.com answers our proxy with 403 (10). Every change still ships as a 2.1.x patch with no breaking-change heading. 2.1.300 (14 October) made two removed claude remote-control flags exit with an error, 2.1.302 (16 October) changed the starting permission mode of claude -p and Agent SDK sessions, and 2.1.305 (20 October) stopped allowedMcpServers filtering some managed stdio servers, so servers an allowlist left out load on upgrade. A stable channel skips releases with major regressions (5). 2.1.318, so 1.0 or later (15). 20 + 0 + 10 + 5 + 15 = 50. Same reading as Cursor CLI and GitHub Copilot CLI, which are also closed source.

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.