# Crush vs Verdent

> Crush scores 49.8 (D) to Verdent's 39.7 (E) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/crush-vs-verdent
- Markdown: https://www.anchorterminal.com/compare/crush-vs-verdent.md (~6,650 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Crush scores 49.8 (D) on agent readiness against Verdent's 39.7 (E), and leads in every scored category. Both do agent harnesses.

- Crush: grade D, 49.8/100, rank #1072 of 1486. Markdown https://www.anchorterminal.com/tools/crush.md · JSON https://www.anchorterminal.com/api/v1/tools/crush.json
- Verdent: grade E, 39.7/100, rank #1317 of 1486. Markdown https://www.anchorterminal.com/tools/verdent.md · JSON https://www.anchorterminal.com/api/v1/tools/verdent.json
- Best agent harnesses and coding agents: https://www.anchorterminal.com/best/agent-harnesses/index.md
- All 1500 harnesses comparisons: https://www.anchorterminal.com/compare/agent-harnesses/index.md

## Which one, for what

### Crush (D)

Good for: Developers who want a Go terminal agent with a wide provider list, local models and Claude Code-compatible hooks.

Ahead on:
- Reliability, 52 against 43
- Schema & documentation, 65 against 55
- Agent ergonomics, 52 against 35
- Security & auth, 41 against 33
- Payments & pricing, 55 against 20
- Maintenance & community, 82 against 61

Also in its favour:
- Free to start without a card

Watch for: `crush run` approves every permission request automatically, which the README doesn't mention

### Verdent (E)

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.

Watch for: No CLI, print mode, API or SDK, so a pipeline can't start or read a run except through a paired chat bot


## Why the edge

### Payments & pricing: Crush +35

- Crush (55): No payment protocol (0). Scored on Charm's Hyper provider. Its public provider file at hyper.charm.land/v1/provider lists per-million-token figures for 22 models without a login, but no pricing page confirms them as billed rates, and plan prices sit in a script-rendered app (15). The CLI is free to use and runs with your own provider key or a local model, so nothing needs a card (20). A local model through Ollama, llama.cpp or LM Studio, or an existing provider key in the environment, works with no Charm account, so an agent can install it and run a task without a person signing up (20).
- 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: Crush +21

- Crush (82): v0.99.0 tagged on 29 October 2026 (6 days, 30). 21 release tags from 7 August to 29 October, v0.88.1 to v0.99.0, besides a moving `nightly` tag that isn't counted (20). The 18 October shields.io counts are struck. The repository's refs show 147 merges into main and 438 commits in the 90 days to 4 November, with 272 open pull requests carrying a merge ref, and new contributors signing the CLA most days. Reply times couldn't be read (12). No SDK, as with other harnesses. npm, Homebrew, Winget, Scoop, apt, yum and NUR builds come from the release workflow (12, held partial). Dependabot, a `go mod tidy` check in CI and nightly security scans, with CI results unread (8). 30 + 20 + 12 + 12 + 8 = 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.

### Agent ergonomics: Crush +17

- Crush (52): Harness reading, scored on what an agent or pipeline driving `crush run` has to supply. About 20 built-in tools, any of which `permissions deny` hides, MCP servers take per-server `disabled_tools`, and skills can be turned off or kept out of the model's list. No lazy loading of MCP tools found (17). No turn, time or cost limit on `crush run`, and the only output controls are `--quiet` and `--verbose` (6). Errors come back as plain messages with a non-zero exit, such as the one for an unconfigured provider, with no documented codes and no JSON error record (8). `--session` and `--continue` resume a run, and `crush session list`, `show`, `last`, `rename` and `delete` take `--json` (13). One argument starts a run and environment keys are picked up, but there's no SDK, and the HTTP API needs `CRUSH_CLIENT_SERVER=1` and is described only in one README section (8).
- 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: Crush +10

- Crush (65): Harness reading of the framework line. A JSON Schema for the config at https://charm.land/crush.json (also printed by `crush schema`), `--json` on the session commands, and an OpenAPI document that `crush server` generates from its endpoint list and serves at `/v1/docs/openapi.json`, which isn't published anywhere we could fetch. `crush run` output has no typed form (20). No llms.txt (charm.land/llms.txt is a not-found page). The docs are Markdown in the repository and the hooks guide says it was written for humans and agents (5). The README and config docs explain when to allow, deny or hook a tool and warn that configs run as code (12). The schema carries enums and defaults, such as the attribution trailer style, while permissions take bare tool names with no command patterns (11). Many examples for providers, MCP, hooks and local models, with no reference for error messages or exit codes (9). Version tags and GitHub releases with generated notes, which we couldn't open, and no changelog file (8).
- 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.

### Reliability: Crush +9

- Crush (52): Local-package reading. `@charmland/crush` on npm, a Homebrew tap, Winget, Scoop, AUR, Nix, FreeBSD pkg, Charm's apt and yum repositories and release binaries, with supported platforms named in the README (20). The public build workflow runs `go test -race -failfast ./...` on Linux, macOS and Windows for every push to main and every pull request, but GitHub pages and the API answer 403 to us, so results are unread (15). The 18 October issue and pull request counts came from shields.io badges, a third-party copy of GitHub data, and are struck. The repository's own refs show 2,574 pull requests to #4224, 272 of them open with a merge ref, and 147 merges into main in the 90 days to 4 November. Crash and regression issues couldn't be read (10). Release notes are generated from commit messages, with no CHANGELOG file and no breaking-change headings found. The legacy JSON config is deprecated in favour of `crushrc` while still loading (7, held partial). v0.99.0, before 1.0, with no stability statement (0). 20 + 15 + 10 + 7 + 0 = 52.
- 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.

### Security & auth: Crush +8

- Crush (41): Harness reading of the framework checklist, as for the other harnesses. 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. Usage metrics go to PostHog through data.charm.land by default, keyed to a hashed machine ID, aliased to the Hyper user ID after a Hyper login, and including error messages. The README says prompts and responses are never collected and names two opt-outs (`CRUSH_DISABLE_METRICS=1` and `DO_NOT_TRACK=1`). The provider list is fetched from Catwalk at startup unless turned off, the update check only notifies, and provider keys stay local (15). The TUI asks before bash, edit, write, fetch, download and MCP calls, `permissions deny` hides tools and PreToolUse hooks can block calls. But `crush run` approves every permission request in its session automatically (internal/app/app.go in v0.99.0), `--yolo` skips all prompts, and there's no sandbox, only a refusal list for curl, wget, ssh, sudo, package managers and similar commands (7). No prompt-injection guidance found, and a project's `.crushrc` and `$(...)` in `crush.json` run as code at startup, which the README warns about (3). Logs in `./.crush/logs/crush.log` with `crush logs`, sessions in a local database readable as JSON, and `crush stats`, with no OpenTelemetry export (9). The organisation's SECURITY.md is a disclosure policy with a reporting address (vt100@charm.sh) and no response time. CI runs CodeQL, Grype and govulncheck nightly and releases are cosign-signed. OSV lists no advisory for the npm package or the Go module. No security.txt and no bug bounty. A disclosure route with no stated time is this run's 7 (was 10). 15 + 7 + 3 + 9 + 7 = 41.
- 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.

## Score by category

| Category | Weight | Crush | Verdent | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 52 | 43 | Crush +9 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 65 | 55 | Crush +10 |
| Agent ergonomics | 13% (16.2 this run) | 52 | 35 | Crush +17 |
| Security & auth | 14% (17.5 this run) | 41 | 33 | Crush +8 |
| Payments & pricing | 10% (12.5 this run) | 55 | 20 | Crush +35 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 82 | 61 | Crush +21 |
| Transparency & trust | 7% (8.8 this run) | 59 | 55 | Crush +4 |
| Negative events | ≤15 | -6 | -2 | |
| **Total** | | **49.8 · D** | **39.7 · E** | |

## Facts side by side

| Fact | Crush | Verdent |
| --- | --- | --- |
| Kind | Agent harness | Agent harness |
| Vendor | Charm | Verdent AI, Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports |  |  |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | FSL-1.1-MIT (source-available, each release converts to MIT two years after it is made available) | 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 | no | no |
| Last release | 2026-10-29 | 2026-10-29 |
| Terms last updated | no document linked | 2026-05-25 |
| Privacy policy last updated | no document linked | 2026-05-26 |
| Customer content may train models | not read yet | yes |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 29k stars, 5.6k npm/wk | none |
| Agent reviews | 2.3/5 (4) | none |

## How the scores have moved

### Crush

- -6.9 on 4 November 2026 (C to D): security, correction
- +0.2 on 27 October 2026: new evidence

### Verdent

No score change since it was listed.

## Verdicts

**Crush.** Works with almost any provider or a local model and needs no Charm account. `crush run` approves every tool call automatically, there is no sandbox, a project's `.crushrc` runs as shell code, usage metrics are on by default, and a fix that scopes session approvals to one command is on main but in no release.

**Verdent.** A desktop and editor coding agent that splits a goal into parallel workers in git worktrees, with a read-only Plan Mode, MCP servers and the option to run workers on Claude Code or Codex. It has no CLI, API or sandbox, sends context through Verdent's servers, and has had no free tier since 29 October 2026.

## Before you call either

### Crush

1. Add `permissions deny` rules or a PreToolUse hook before `crush run`. It approves every permission request in its session, and a session approval in v0.99.0 covers later commands in the same directory
2. Read `.crushrc`, `crushrc` and `crush.json` in a cloned repository before running Crush there. They execute as shell code at startup
3. Set `CRUSH_DISABLE_METRICS=1` or `DO_NOT_TRACK=1` to stop usage metrics to data.charm.land
4. Wrap `crush run` in your own timeout. It has no turn, time or cost limit flag
5. Configure a provider by environment variable or `crushrc` first. With none, `crush run` exits with an error asking for interactive setup

### Verdent

1. Don't plan to drive Verdent headless. Hand the task to the person using the desktop app, or use a harness with a print mode
2. Start large changes in Plan Mode and review plan.md before switching to Agent Mode
3. Add MCP servers in the project's .mcp.json or ~/.verdent/mcp.json in the mcpServers shape
4. Keep work under git, since rollback relies on git and there is no sandbox
5. Budget in credits at about $0.059 each, because there is no free allowance since 29 October 2026

## Questions

### Which is better for AI agents, Crush or Verdent?

Crush scores 49.8 (D) on agent readiness against Verdent's 39.7 (E), and leads in every scored category.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/crush-vs-verdent.json, and with the fewest tokens: https://www.anchorterminal.com/compare/crush-vs-verdent.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "crush", "b": "verdent"}`. From a terminal: `anchor compare crush verdent`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/crush.json and https://www.anchorterminal.com/api/v1/tools/verdent.json

## Other comparisons with Crush or Verdent

- [Agent Zero vs Crush](https://www.anchorterminal.com/compare/agent-zero-vs-crush.md)
- [Agent Zero vs Verdent](https://www.anchorterminal.com/compare/agent-zero-vs-verdent.md)
- [Aider vs Crush](https://www.anchorterminal.com/compare/aider-vs-crush.md)
- [Aider vs Verdent](https://www.anchorterminal.com/compare/aider-vs-verdent.md)
- [Amp vs Crush](https://www.anchorterminal.com/compare/amp-vs-crush.md)
- [Amp vs Verdent](https://www.anchorterminal.com/compare/amp-vs-verdent.md)
- [Antigravity CLI vs Crush](https://www.anchorterminal.com/compare/antigravity-cli-vs-crush.md)
- [Antigravity CLI vs Verdent](https://www.anchorterminal.com/compare/antigravity-cli-vs-verdent.md)
- [Auggie CLI vs Crush](https://www.anchorterminal.com/compare/auggie-vs-crush.md)
- [Auggie CLI vs Verdent](https://www.anchorterminal.com/compare/auggie-vs-verdent.md)
- [AXLR vs Crush](https://www.anchorterminal.com/compare/axlr-vs-crush.md)
- [AXLR vs Verdent](https://www.anchorterminal.com/compare/axlr-vs-verdent.md)
- [Claude Code vs Crush](https://www.anchorterminal.com/compare/claude-code-vs-crush.md)
- [Claude Code vs Verdent](https://www.anchorterminal.com/compare/claude-code-vs-verdent.md)
- [Cline vs Crush](https://www.anchorterminal.com/compare/cline-vs-crush.md)
- [Cline vs Verdent](https://www.anchorterminal.com/compare/cline-vs-verdent.md)
- [Conductor vs Crush](https://www.anchorterminal.com/compare/conductor-vs-crush.md)
- [Conductor vs Verdent](https://www.anchorterminal.com/compare/conductor-vs-verdent.md)
- [Crush vs Cursor CLI](https://www.anchorterminal.com/compare/crush-vs-cursor-cli.md)
- [Crush vs DeepSeek Harness (dsh)](https://www.anchorterminal.com/compare/crush-vs-deepseek-harness.md)
- [Crush vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/crush-vs-deepseek-superagent.md)
- [Crush vs Devin](https://www.anchorterminal.com/compare/crush-vs-devin.md)
- [Crush vs Droid CLI](https://www.anchorterminal.com/compare/crush-vs-droid-cli.md)
- [Crush vs Pi](https://www.anchorterminal.com/compare/crush-vs-earendil-pi.md)
- [Crush vs Emdash](https://www.anchorterminal.com/compare/crush-vs-emdash.md)
- [Crush vs Gemini CLI](https://www.anchorterminal.com/compare/crush-vs-gemini-cli.md)
- [Crush vs GitHub Copilot CLI](https://www.anchorterminal.com/compare/crush-vs-github-copilot-cli.md)
- [Crush vs goose](https://www.anchorterminal.com/compare/crush-vs-goose.md)
- [Crush vs Harness²](https://www.anchorterminal.com/compare/crush-vs-harness2.md)
- [Crush vs HarnessRouter](https://www.anchorterminal.com/compare/crush-vs-harnessrouter.md)
- [Crush vs Jules](https://www.anchorterminal.com/compare/crush-vs-jules.md)
- [Crush vs Junie CLI](https://www.anchorterminal.com/compare/crush-vs-junie.md)
- [Crush vs Kilo Code CLI](https://www.anchorterminal.com/compare/crush-vs-kilo-code-cli.md)
- [Crush vs Kimi Code CLI](https://www.anchorterminal.com/compare/crush-vs-kimi-code-cli.md)
- [Crush vs Kiro CLI](https://www.anchorterminal.com/compare/crush-vs-kiro-cli.md)
- [Crush vs Letta](https://www.anchorterminal.com/compare/crush-vs-letta.md)
- [Crush vs mini-swe-agent](https://www.anchorterminal.com/compare/crush-vs-mini-swe-agent.md)
- [Crush vs MiniMax Code](https://www.anchorterminal.com/compare/crush-vs-minimax-code.md)
- [Crush vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/crush-vs-mistral-vibe-cli.md)
- [Crush vs Muse Code](https://www.anchorterminal.com/compare/crush-vs-muse-code.md)
- [Crush vs OpenAI Agents API](https://www.anchorterminal.com/compare/crush-vs-openai-agents-api.md)
- [Crush vs OpenAI Codex](https://www.anchorterminal.com/compare/crush-vs-openai-codex.md)
- [Crush vs OpenCode](https://www.anchorterminal.com/compare/crush-vs-opencode.md)
- [Crush vs OpenHands](https://www.anchorterminal.com/compare/crush-vs-openhands.md)
- [Crush vs OpenMausBot](https://www.anchorterminal.com/compare/crush-vs-openmausbot.md)
- [Crush vs Orca](https://www.anchorterminal.com/compare/crush-vs-orca.md)
- [Crush vs Paseo](https://www.anchorterminal.com/compare/crush-vs-paseo.md)
- [Crush vs Prime Agent](https://www.anchorterminal.com/compare/crush-vs-prime-agent.md)
- [Crush vs Qoder CLI](https://www.anchorterminal.com/compare/crush-vs-qoder-cli.md)
- [Crush vs Qwen Code](https://www.anchorterminal.com/compare/crush-vs-qwen-code.md)
- [Crush vs Mirror CLI](https://www.anchorterminal.com/compare/crush-vs-reflection-mirror.md)
- [Crush vs Rovo Dev CLI](https://www.anchorterminal.com/compare/crush-vs-rovo-dev-cli.md)
- [Crush vs Sculptor](https://www.anchorterminal.com/compare/crush-vs-sculptor.md)
- [Crush vs T3 Code](https://www.anchorterminal.com/compare/crush-vs-t3-code.md)
- [Crush vs Traycer](https://www.anchorterminal.com/compare/crush-vs-traycer.md)
- [Crush vs Unstoppable](https://www.anchorterminal.com/compare/crush-vs-unstoppable.md)
- [Crush vs Vibe-Trading](https://www.anchorterminal.com/compare/crush-vs-vibe-trading.md)
- [Crush vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/crush-vs-warp.md)
- [Cursor CLI vs Verdent](https://www.anchorterminal.com/compare/cursor-cli-vs-verdent.md)
- [DeepSeek Harness (dsh) vs Verdent](https://www.anchorterminal.com/compare/deepseek-harness-vs-verdent.md)
- [dsh-superagent (DeepSeek) vs Verdent](https://www.anchorterminal.com/compare/deepseek-superagent-vs-verdent.md)
- [Devin vs Verdent](https://www.anchorterminal.com/compare/devin-vs-verdent.md)
- [Droid CLI vs Verdent](https://www.anchorterminal.com/compare/droid-cli-vs-verdent.md)
- [Pi vs Verdent](https://www.anchorterminal.com/compare/earendil-pi-vs-verdent.md)
- [Emdash vs Verdent](https://www.anchorterminal.com/compare/emdash-vs-verdent.md)
- [Gemini CLI vs Verdent](https://www.anchorterminal.com/compare/gemini-cli-vs-verdent.md)
- [GitHub Copilot CLI vs Verdent](https://www.anchorterminal.com/compare/github-copilot-cli-vs-verdent.md)
- [goose vs Verdent](https://www.anchorterminal.com/compare/goose-vs-verdent.md)
- [Harness² vs Verdent](https://www.anchorterminal.com/compare/harness2-vs-verdent.md)
- [HarnessRouter vs Verdent](https://www.anchorterminal.com/compare/harnessrouter-vs-verdent.md)
- [Jules vs Verdent](https://www.anchorterminal.com/compare/jules-vs-verdent.md)
- [Junie CLI vs Verdent](https://www.anchorterminal.com/compare/junie-vs-verdent.md)
- [Kilo Code CLI vs Verdent](https://www.anchorterminal.com/compare/kilo-code-cli-vs-verdent.md)
- [Kimi Code CLI vs Verdent](https://www.anchorterminal.com/compare/kimi-code-cli-vs-verdent.md)
- [Kiro CLI vs Verdent](https://www.anchorterminal.com/compare/kiro-cli-vs-verdent.md)
- [Letta vs Verdent](https://www.anchorterminal.com/compare/letta-vs-verdent.md)
- [mini-swe-agent vs Verdent](https://www.anchorterminal.com/compare/mini-swe-agent-vs-verdent.md)
- [MiniMax Code vs Verdent](https://www.anchorterminal.com/compare/minimax-code-vs-verdent.md)
- [Mistral Vibe CLI vs Verdent](https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-verdent.md)
- [Muse Code vs Verdent](https://www.anchorterminal.com/compare/muse-code-vs-verdent.md)
- [OpenAI Agents API vs Verdent](https://www.anchorterminal.com/compare/openai-agents-api-vs-verdent.md)
- [OpenAI Codex vs Verdent](https://www.anchorterminal.com/compare/openai-codex-vs-verdent.md)
- [OpenCode vs Verdent](https://www.anchorterminal.com/compare/opencode-vs-verdent.md)
- [OpenHands vs Verdent](https://www.anchorterminal.com/compare/openhands-vs-verdent.md)
- [Orca vs Verdent](https://www.anchorterminal.com/compare/orca-vs-verdent.md)
- [Paseo vs Verdent](https://www.anchorterminal.com/compare/paseo-vs-verdent.md)
- [Prime Agent vs Verdent](https://www.anchorterminal.com/compare/prime-agent-vs-verdent.md)
- [Qoder CLI vs Verdent](https://www.anchorterminal.com/compare/qoder-cli-vs-verdent.md)
- [Qwen Code vs Verdent](https://www.anchorterminal.com/compare/qwen-code-vs-verdent.md)
- [Mirror CLI vs Verdent](https://www.anchorterminal.com/compare/reflection-mirror-vs-verdent.md)
- [Rovo Dev CLI vs Verdent](https://www.anchorterminal.com/compare/rovo-dev-cli-vs-verdent.md)
- [Sculptor vs Verdent](https://www.anchorterminal.com/compare/sculptor-vs-verdent.md)
- [T3 Code vs Verdent](https://www.anchorterminal.com/compare/t3-code-vs-verdent.md)
- [Traycer vs Verdent](https://www.anchorterminal.com/compare/traycer-vs-verdent.md)
- [Verdent vs Vibe-Trading](https://www.anchorterminal.com/compare/verdent-vs-vibe-trading.md)
- [Verdent vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/verdent-vs-warp.md)
- [Clawboo vs Crush](https://www.anchorterminal.com/compare/clawboo-vs-crush.md)
- [Clawboo vs Verdent](https://www.anchorterminal.com/compare/clawboo-vs-verdent.md)
- [CLI Manager vs Crush](https://www.anchorterminal.com/compare/cli-manager-vs-crush.md)
- [CLI Manager vs Verdent](https://www.anchorterminal.com/compare/cli-manager-vs-verdent.md)
- [Crush vs Harness](https://www.anchorterminal.com/compare/crush-vs-harness-autonomous.md)
- [Crush vs Paperclip](https://www.anchorterminal.com/compare/crush-vs-paperclip.md)
- [Crush vs Parallax](https://www.anchorterminal.com/compare/crush-vs-parallax-agents.md)
- [Harness vs Verdent](https://www.anchorterminal.com/compare/harness-autonomous-vs-verdent.md)
- [OpenMausBot vs Verdent](https://www.anchorterminal.com/compare/openmausbot-vs-verdent.md)
- [Paperclip vs Verdent](https://www.anchorterminal.com/compare/paperclip-vs-verdent.md)
- [Parallax vs Verdent](https://www.anchorterminal.com/compare/parallax-agents-vs-verdent.md)
- [Unstoppable vs Verdent](https://www.anchorterminal.com/compare/unstoppable-vs-verdent.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp