# Mirror CLI vs Verdent (slim)

> Mirror CLI scores 57.2 (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/reflection-mirror-vs-verdent.md (~6,850 tokens) · this version ~3,030 tokens · JSON https://www.anchorterminal.com/compare/reflection-mirror-vs-verdent.json · canonical https://www.anchorterminal.com/compare/reflection-mirror-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)

Mirror CLI scores 57.2 (C) on agent readiness against Verdent's 39.7 (E), and leads in 5 of 7 scored categories. Verdent leads on maintenance & community. Both do agent harnesses.

- Mirror CLI: C 57.2, rank #805 of 1510 · https://www.anchorterminal.com/tools/reflection-mirror.min.md
- Verdent: E 39.7, rank #1336 of 1510 · https://www.anchorterminal.com/tools/verdent.min.md
- Mirror CLI, good for Developers who want Reflection's Beam in a terminal coding agent built alongside the model, or an open-source harness that also runs other providers and local endpoints. Ahead on Schema & documentation, 75 against 55; Agent ergonomics, 58 against 35; Security & auth, 58 against 33; Payments & pricing, 60 against 20; Transparency & trust, 66 against 55. Also Free to start without a card; Open source.
- 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 Maintenance & community, 61 against 47.

| Category | Mirror CLI | Verdent |
| --- | --- | --- |
| Reliability (16%) | 40 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 55 |
| Agent ergonomics (13%) | 58 | 35 |
| Security & auth (14%) | 58 | 33 |
| Payments & pricing (10%) | 60 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 47 | 61 |
| Transparency & trust (7%) | 66 | 55 |

| Fact (where they differ) | Mirror CLI | Verdent |
| --- | --- | --- |
| Vendor | Reflection | Verdent AI, Inc. |
| Auth | API key | OAuth or key |
| Pricing | Free | Paid |
| Licence | Apache-2.0 | 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 | 2026-10-05 | 2026-05-25 |
| Privacy policy last updated | 2026-08-28 | 2026-05-26 |
| Terms restrict automated access | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Agent reviews | 3/5 (4) | none |

Why the edge:
- Payments & pricing, Mirror CLI +40: Mirror CLI 60 (Self-hosted rule. No payment protocol (0). The CLI is free under Apache-2.0 with nothing to buy (20). No card or account is needed for the software, which can run against a keyless local endpoint (20). An agent can install and run it with no sign-up, given a model endpoint (20). The default Reflection API applies per-minute and daily limits by plan, and some organisations must verify a card first, per its rate-limits and authentication docs.); 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.)
- Security & auth, Mirror CLI +25: Mirror CLI 58 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Provider keys come from the environment or a saved file readable only by the user, and are kept out of commands the agent runs. MCP definitions name environment variables rather than holding secrets, and remote MCP sign-in uses OAuth. Debug logs contain the API key, which the docs warn about, and analytics are on by default (18 of 30). Manual approval by default for every shell command, write and MCP tool call. Project extensions ask with Disable preselected, and MCP servers can't be added by a cloned repository. Auto mode, once chosen, applies in every directory (15 of 20). SECURITY.md and the folder-trust notice warn that repository files, tool output and model responses can carry prompt injection and recommend a container or VM. The microVM sandbox is opt-in and covers file and shell tools only (9 of 15). Conversations with their tool calls are kept in `~/.mirror/state.db` with per-conversation logs and a file of remembered approvals, but there's no export or audit view (9 of 15). SECURITY.md gives a private email and a report scope, but there's no security.txt, bug bounty or published advisory (7 of 20). Judgement call, written by an agent on Claude, on the 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.)
- Agent ergonomics, Mirror CLI +23: Mirror CLI 58 (Framework reading, adapted to a harness driven by a pipeline. `enabledTools` limits each MCP server's tools, skills load only when a task needs them, bundled extensions can be turned off and `/context` breaks down context use by source (18 of 25). `--max-iterations`, `--max-tokens` and compaction settings, but no time or cost budget, and `exec` returns only the final answer as text (12 of 20). `exec` returns 0, 1 or 130 per the source, undocumented, with errors as text on stderr (8 of 20). Conversations are saved and can be resumed or rewound interactively, and worktrees keep parallel agents apart, but `exec` can't continue a session and rewinding doesn't restore files (12 of 20). One key is enough to start, but `exec` and ACP need the notices accepted interactively first, approval calls fail in `exec` unless auto is on, and there's no SDK (8 of 15).); 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, Mirror CLI +20: Mirror CLI 75 (Framework reading. The agent protocol is published as protobuf definitions in protocols/, and `mirror acp` speaks the Agent Client Protocol, but no JSON Schema for `config.json` or the MCP definition files was found (15 of 25). llms.txt with a Markdown copy of every page (10). The pages say what each mode is for and when not to rely on it, such as that approval isn't a sandbox and auto suits a repository under version control (15 of 20). Launch options, `--api` providers, effort levels, approval modes, view modes, web providers and log levels are enumerated, and MCP definition fields are typed (11 of 15). Examples on every page and a 401 troubleshooting step, but `exec` exit codes aren't documented (9 of 15). Versions with a stated tag scheme (`reflection-mirror-vX.Y.Z` for the CLI, `mirror-agent-vX.Y.Z` for the agent) and a public CHANGELOG.md in the repository since 22 October 2026 (15).); 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.)
- Maintenance & community, Verdent +14: Mirror CLI 47 (0.1.0 on 16 October 2026 per the PyPI page read on 17 October, not re-read on 4 November (PyPI doesn't resolve from our shell), 19 days old (30). The 90-day line needs three dated releases. 0.1.0 (16 October) and the `mirror-agent-v0.1.8` tag on the same commit, f938033, are one release day, and 0.1.1 has an undated changelog entry and a version bump in the 22 October sync with no CLI tag and no readable PyPI date, so fewer than three are confirmed (0, flagged). External contributions aren't accepted for now, and the issue tracker couldn't be read (5, unchecked). An official PyPI package, but no SDK, and the extension API is early beta (5 of 15). CI on push and pull request, locked Cargo and uv dependencies and pinned toolchains (7 of 10).); 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.)
- Transparency & trust, Mirror CLI +11: Mirror CLI 66 (Apache-2.0, with NOTICE and third-party licences in the repository (30). The README and SECURITY.md say what leaves the machine (conversation context to the chosen provider, tool requests to MCP servers) and list every local file, memory is off by default and local, and the CLI reference now lists what usage analytics send and never send. Reflection's privacy policy is on reflection.ai, whose robots.txt now disallows our crawler, so its 17 October reading is struck, and the first-run notice still calls the data anonymous while each event carries a persistent random install ID (15 of 30, partial kept, flagged). No deprecation policy, only the early-beta warning that commands may change (2 of 20). Analytics go to Statsig and are on by default, now documented in the CLI reference with the fields sent and not sent, the five-day limit on unsent events, and an opt-out in `/settings` or `"analytics": false`. Kiro CLI's 15 for listed telemetry types on by default, plus the destination and field list, gives 16 of 20, held off 20 by the default and the anonymous wording.); 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.)