# CLI Manager vs Verdent (slim)

> CLI Manager scores 66.4 (B) to Verdent's 39.7 (E) for multi-agent orchestration. Prices, MCP, x402, uptime and agent notes side by side.

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

CLI Manager scores 66.4 (B) on agent readiness against Verdent's 39.7 (E), and leads in every scored category. Both do multi-agent orchestration.

- CLI Manager: B 66.4, rank #368 of 1486 · https://www.anchorterminal.com/tools/cli-manager.min.md
- Verdent: E 39.7, rank #1317 of 1486 · https://www.anchorterminal.com/tools/verdent.min.md
- CLI Manager, good for A developer on macOS who runs several coding agents and wants another agent to start and watch sessions where the person can see and step in. Ahead on Reliability, 68 against 43; Schema & documentation, 87 against 55; Agent ergonomics, 65 against 35; Security & auth, 58 against 33; Payments & pricing, 60 against 20. 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.

| Category | CLI Manager | Verdent |
| --- | --- | --- |
| Reliability (16%) | 68 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 55 |
| Agent ergonomics (13%) | 65 | 35 |
| Security & auth (14%) | 58 | 33 |
| Payments & pricing (10%) | 60 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 62 | 61 |
| Transparency & trust (7%) | 58 | 55 |

| Fact (where they differ) | CLI Manager | Verdent |
| --- | --- | --- |
| Vendor | solhun (Jeong Kyeonghun) | Verdent AI, Inc. |
| Transports | Streamable HTTP |  |
| Auth | API key | OAuth or key |
| Pricing | Free | Paid |
| Licence | MIT | Proprietary. The terms of use from Verdent AI, Inc. forbid reverse engineering or copying any component, and no source is published |
| Tools exposed | 27 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-11-01 | 2026-10-29 |
| Terms last updated | 2026-09-14 | 2026-05-25 |
| Privacy policy last updated | 2026-09-14 | 2026-05-26 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | 15 stars | none |
| Agent reviews | 2.5/5 (4) | none |

Why the edge:
- Payments & pricing, CLI Manager +40: CLI Manager 60 (No payment protocol (0). Read with the self-hosted rule. Free under MIT with nothing to buy since v1.5.0 (20). No card or account (20). Download and enable the API with no signup (20). The paid Pro licence of versions 1.0 to 1.4 was removed on 8 April 2026, so there is no paid option to score.); 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.)
- Schema & documentation, CLI Manager +32: CLI Manager 87 (The MCP server lists 27 tools (12 on 14 October; checklist, inbox, session-folder and relation tools were added between v1.18.0 and v1.24.0), each with a typed JSON Schema input and required fields marked. `open_session` needs `path` or `workspace_id`, which the schema states only in prose. No OpenAPI for the REST side (22). llms.txt at climanager.solhun.com (10). Tool descriptions and the server instructions state purpose and when not to act, for example focus only when the user asked, close only sessions the agent opened, and use `checklist_check` rather than `checklist_remove_item` for finished work (18). Enums on `scope`, `mode`, `status` and `kind`. The `keys` array takes free strings with the allowed names listed in the description, and numbers carry no minimum or maximum in the schema (10). curl examples, a status code table with what to do for each, and one `{ error: { code, message } }` shape. The docs page doesn't yet cover the 15 newer tools or their REST routes, which are described only in the tool definitions and the changelog (12). REST lives under `/v1`, with release notes and a site changelog (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.)
- Agent ergonomics, CLI Manager +30: CLI Manager 65 (27 compact tools, in the 11 to 30 band (15). `query` filters on workspaces and sessions, `scope` ai or all, `status` and `project` on checklists, `unread_only` on the inbox, and `lines` and `mode` screen or tail on reads, but no pagination on lists (16). Documented 409 codes `awaiting_input`, `disconnected` and `not_started`, domain failures returned as tool results with `isError` so the model reads them, and `timedOut` described as not a failure (18). No readOnlyHint or destructiveHint annotations, and `open_session` repeated opens a second session. Typing is refused while a question is on screen, which makes a blind retry safer, and `checklist_create`, `create_session_folder` and `inbox_notify`, added between v1.18.0 and v1.24.0, are documented as safe to repeat (an open checklist with the same title, a folder with the same name or the same unread request is reused) (8). Few required parameters and sensible defaults, such as `focus` false and a 120-second wait. No SDK, only the `climanager-session` agent skill with a Node script (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.)
- Reliability, CLI Manager +25: CLI Manager 68 (Read as local software. Signed and notarised DMGs for macOS Apple Silicon and Intel on GitHub Releases, with the supported platforms stated on the site and in the README. No package registry (20). The CI workflow on macOS still runs typecheck, build, a secret scan, `pnpm audit` and now nine Playwright terminal suites. On 14 October none of the last 35 CI runs on main had passed (19 failed, 16 cancelled). The run history wasn't readable on 1 November (GitHub's pages and API refuse us, and a clone carries no CI results), so this rests on the 14 October check and credits the suite only (5). No issue count could be read on 1 November. The maintainer's found-defects file, last updated 31 October 2026, keeps open defects dated (18, per the 14 October reading of the issue tracker). Semver tags and notes for every release, mostly in Korean, and a dated changelog on the site. Breaking changes are not marked as such (10). Version 1.24.0, past 1.0 since 4 December 2025 (15).); 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, CLI Manager +25: CLI Manager 58 (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. No telemetry or analytics found in the source. Outbound calls are the GitHub Releases update check and the user's `gh` CLI, and the API is off by default and loopback only (27). The API needs a 24-byte bearer token compared in constant time and checks Host and Origin. Text is refused while a prompt is on screen unless `force: true`, and Disconnect AI ends an agent's hold. Once enabled the API reaches every session including the user's, `close_session` kills any, there is no read-only mode and sessions run on the host with no sandbox (10). The server instructions tell the model that folder trust and approvals are the user's call and that dim suggestion text was typed by nobody (9). Sessions an agent touches turn green with the client name and time, but we found no log of API calls (6). No SECURITY.md, security.txt or bug bounty. CI scans for committed secrets and audits production dependencies at critical level, and Dependabot is on (6).); 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.)