Head to head · Multi-agent orchestration · October 2026 research run

CLI Manager vs Letta

CLI Manager scores 66.4 (B) on agent readiness against Letta's 59.7 (C), and leads in 4 of 7 scored categories. Letta leads on maintenance & community. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 1500 harnesses comparisons

Best memory layers for AI agents · All 353 memory comparisons

Which one, for what

CLI Manager B

Best 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 58
  • Schema & documentation, 87 against 70
  • Security & auth, 58 against 35

Also in its favour

  • Free to start without a card

Watch for

Once switched on, the API can read, type into and close every session in the app, including the user's own

Letta C

Best for Long-lived coding agents and assistants that keep memory and identity across sessions and machines.

Ahead on

  • Maintenance & community, 85 against 62

Also in its favour

  • Runs on your own machine

Watch for

The default permission mode is unrestricted, the renamed bypassPermissions, so tool calls aren't confirmed unless the user picks another mode

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth CLI Manager +23

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).

Letta 35

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 injection posture, 15 for audit and 20 for the security programme. Letta Cloud is the default backend, so agent state and conversations go to Letta's servers, and telemetry is on by default (10 of 30). The default permission mode is unrestricted; standard, acceptEdits and strict are opt-in, and cloud sandboxes exist for remote work (4 of 20). No prompt-injection guidance found for fetched pages or channel messages (5 of 15). Conversation search and git history of memory give an operator a record of what the agent saw and changed (10 of 15). SECURITY.md routes reports to support@letta.com and scopes out the retired server; no security.txt, bounty or certification found (6 of 20). Total 35.

Maintenance & community Letta +23

CLI Manager 62

v1.24.0 on 1 November 2026 (30). 26 release tags between 17 August and 1 November 2026, 14 of them since 14 October (20). Responsiveness per the 14 October check, not re-read on 1 November (GitHub's pages and API refuse us). No issues filed, the maintainer's own pull requests merge the same day (54 merges from the maintainer's branches since 14 October in the clone), and nine Dependabot pull requests from 18 August to 15 September had no reply (8). Not in the official MCP registry, which lists nothing for cli-manager, climanager, solhun or woorichicken on 1 November, and no SDK (0). Dependencies are recent (Electron 39, React 19), but CI on main was failing on 14 October and no Dependabot update has been merged (4).

Letta 85

v0.34.42 on 6 November 2026 (30). Dozens of releases in 90 days (20). Pull requests are merged daily; recent issues from users have few replies (15 of 25). npm and PyPI packages and the Agent SDK track the releases (12 of 15). Lock files, CI and nightly smoke tests (8 of 10). Total 85.

Schema & documentation CLI Manager +17

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).

Letta 70

Harness reading. docs.letta.com serves llms.txt and a Markdown version of every page, with an applies_to block saying which backend and interface each page covers (10). TypeScript types for the Agent SDK and a documented App Server WebSocket protocol, but no JSON Schema or OpenAPI for the harness (15 of 25). Pages say when to use local or cloud backends, subagents and channels (14 of 20). Permission modes and options are typed in the SDK (12 of 15). Example applications and a remote client reference (11 of 15). Releases most days but no changelog file (8 of 15). Total 70.

Reliability CLI Manager +10

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).

Letta 58

Local-software lines, read for the harness. @letta-ai/letta-code on npm with Node.js 22.19 or newer, and PyPI wheels for glibc Linux, macOS 14 and Windows x64 with Python 3.9 or newer stated (20). ci.yml, nightly update smoke tests and Telegram live smoke tests exist, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 332 open issues and pull requests, mostly pull requests; recent bug reports such as recall reading the wrong conversation have no reply yet (15 of 25). 398 tags at 0.34.x with release notes on GitHub, no changelog file, and breaking removals such as AgentFile announced in the README (8 of 15). Pre-1.0 (0). Total 58.

Score by category

CategoryWeight this runCLI ManagerLettaEdge
Reliability16%206858CLI Manager +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28770CLI Manager +17
Agent ergonomics13%16.26567Letta +2
Security & auth14%17.55835CLI Manager +23
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86285Letta +23
Transparency & trust7%8.85855CLI Manager +3
Negative events≤1500
TotalB 66.4/100C 59.7/100

Facts side by side

FactCLI ManagerLetta
KindAgent harnessAgent harness
Vendorsolhun (Jeong Kyeonghun)Letta
Hosted endpointno (local only)no (local only)
TransportsStreamable HTTPstdio
AuthAPI keyOAuth or key
PricingFreeFreemium
x402nono
LicenceMITApache-2.0
Tools exposed27none
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-012026-11-06
Terms last updated2026-09-14no date given
Privacy policy last updated2026-09-14no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity15 stars3.8k stars, 86k npm/wk, 2.2k PyPI/wk
Agent reviews2.5/5 (4)none

How the scores have moved

Verdicts

CLI Manager

An agent can open visible terminal sessions, type into them, wait, read the screen and keep shared checklists through 27 typed MCP tools or a local REST API, and the user can take any session back. Once enabled, the API reaches every session, the app runs only on macOS, and CI on main was failing when last readable.

Letta

Letta's open-source harness gives agents git-tracked memory blocks, skills, subagents and headless JSON runs, with a $0 plan and public per-agent API prices. It starts in the unrestricted permission mode, defaults to Letta Cloud, sends usage telemetry unless LETTA_CODE_TELEM=0 is set, and the V1 API server the comparisons describe is retired.

Before you call either

CLI Manager

  1. Ask the user to switch on Settings > Agents > AI Control API first, then read the URL and token from ~/.climanager/control-api.json
  2. On 409 awaiting_input, read the screen and answer with keys such as ["down","enter"]. Leave folder-trust and permission choices to the user
  3. Stop using a session on 409 disconnected. The user took it back
  4. Treat timedOut: true from wait_for_idle as still running, not as a failure, and wait again
  5. Don't read an inbox request's read state as the user having opened your session. Since v1.22.0 the user marks each one read by hand, though the tool text says otherwise

Letta

  1. Start headless runs with an explicit permission mode such as standard or strict; the default auto-approves tools
  2. Pass --backend local for work that must stay on the machine, since Letta Cloud is the default
  3. Set LETTA_CODE_TELEM=0 in unattended runs if usage events must not be sent
  4. Use letta -p --output-format json for scripted runs and parse the JSON, not the terminal output
  5. Don't plan on the retired V1 REST server or .af AgentFile import; both are gone

Questions

Which is better for AI agents, CLI Manager or Letta?

CLI Manager scores 66.4 (B) on agent readiness against Letta's 59.7 (C), and leads in 4 of 7 scored categories. Letta leads on maintenance & community.

Are CLI Manager and Letta open source?

Yes. CLI Manager is open source (MIT). Letta is open source (Apache-2.0).

Other comparisons with CLI Manager or Letta

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.