Head to head · Agent harnesses · October 2026 research run
Letta vs Paseo
Paseo scores 62.1 (B) on agent readiness against Letta's 59.7 (C), and leads in 3 of 7 scored categories. Letta leads on reliability, schema & documentation and maintenance & community. Both do agent harnesses.
Best agent harnesses and coding agents · All 1500 harnesses comparisons
Best memory layers for AI agents · All 353 memory comparisons
Which one, for what
Letta C
Best for Long-lived coding agents and assistants that keep memory and identity across sessions and machines.
Ahead on
- Reliability, 58 against 50
- Schema & documentation, 70 against 65
- Maintenance & community, 85 against 75
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
Paseo B
Best for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere.
Ahead on
- Security & auth, 58 against 35
- Transparency & trust, 68 against 55
Also in its favour
- No key needed to call it
Watch for
Pre-1.0, at 0.15.3
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 Paseo +23
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.
Paseo 58
Harness reading. The README says no telemetry, tracking or forced log-ins (30 of 30). Worktree per agent, on your own machine (10 of 20). No prompt-injection guidance (5). No audit log (5). SECURITY.md (8). 30 + 10 + 5 + 5 + 8 = 58.
Transparency & trust Paseo +13
Letta 55
Apache-2.0 (30). The privacy policy has no date, no legal entity and no retention periods, and says hosted message data may train future models (8 of 30). The README and docs mark AgentFile, the Electron app and the V1 server as deprecated or retired, without dated notice periods (12 of 20). Telemetry is described in the privacy policy only as basic and opt-out when supported; the LETTA_CODE_TELEM=0 switch appears only in the source (5 of 20). Total 55.
Paseo 68
Apache 2.0 for everything but third-party components (30). No telemetry and agents run on your machine (22 of 30). CHANGELOG.md, no deprecation policy (10). States no telemetry (20). 30 + 22 + 10 + 20 = 82.
Maintenance & community Letta +10
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.
Paseo 75
v0.15.3 and commits on 7 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current builds (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.
Reliability Letta +8
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.
Paseo 50
Local software. Desktop builds, an Android APK, a Docker image and a Nix package (20). ci.yml on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Version 0.15.3 (0). 20 + 15 + 0 + 15 + 0 = 50.
Schema & documentation Letta +5
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.
Paseo 65
Harness reading. Public docs, a CLI and plugin examples in the repository (65).
Score by category
| Category | Weight this run | Letta | Paseo | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 58 | 50 | Letta +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 70 | 65 | Letta +5 |
| Agent ergonomics | 13%16.2 | 67 | 70 | Paseo +3 |
| Security & auth | 14%17.5 | 35 | 58 | Paseo +23 |
| Payments & pricing | 10%12.5 | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 85 | 75 | Letta +10 |
| Transparency & trust | 7%8.8 | 55 | 68 | Paseo +13 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 59.7/100 | B 62.1/100 |
Facts side by side
| Fact | Letta | Paseo |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Letta | Mohamed Boudra |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-11-06 | 2026-11-07 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | no date given | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 3.8k stars, 86k npm/wk, 2.2k PyPI/wk | none |
Verdicts
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.
Paseo
A self-hosted, open-source workspace for running many coding agents on your own machines, scriptable from the CLI and reachable from phone, web or desktop, with no telemetry or forced log-in. It's pre-1.0 and run largely by one maintainer.
Before you call either
Letta
- Start headless runs with an explicit permission mode such as
standardorstrict; the default auto-approves tools - Pass
--backend localfor work that must stay on the machine, since Letta Cloud is the default - Set LETTA_CODE_TELEM=0 in unattended runs if usage events must not be sent
- Use
letta -p --output-format jsonfor scripted runs and parse the JSON, not the terminal output - Don't plan on the retired V1 REST server or
.afAgentFile import; both are gone
Paseo
- Run the daemon on the machine that has your tools and credentials, and connect from the clients
- Script runs from the CLI for repeatable agent jobs
Questions
Which is better for AI agents, Letta or Paseo?
Paseo scores 62.1 (B) on agent readiness against Letta's 59.7 (C), and leads in 3 of 7 scored categories. Letta leads on reliability, schema & documentation and maintenance & community.
Are Letta and Paseo open source?
Yes. Letta is open source (Apache-2.0). Paseo is open source (Apache-2.0).
Other comparisons with Letta or Paseo
- Agent Zero vs Letta
- Agent Zero vs Paseo
- Aider vs Letta
- Aider vs Paseo
- Amp vs Letta
- Amp vs Paseo
- Antigravity CLI vs Letta
- Antigravity CLI vs Paseo
- Auggie CLI vs Letta
- Auggie CLI vs Paseo
- AXLR vs Letta
- AXLR vs Paseo
- Claude Code vs Letta
- Claude Code vs Paseo
- Cline vs Letta
- Cline vs Paseo
- Conductor vs Letta
- Conductor vs Paseo
- Crush vs Letta
- Crush vs Paseo
- Cursor CLI vs Letta
- Cursor CLI vs Paseo
- DeepSeek Harness (dsh) vs Letta
- DeepSeek Harness (dsh) vs Paseo
- dsh-superagent (DeepSeek) vs Letta
- dsh-superagent (DeepSeek) vs Paseo
- Devin vs Letta
- Devin vs Paseo
- Droid CLI vs Letta
- Droid CLI vs Paseo
- Pi vs Letta
- Pi vs Paseo
- Emdash vs Letta
- Emdash vs Paseo
- Gemini CLI vs Letta
- Gemini CLI vs Paseo
- GitHub Copilot CLI vs Letta
- GitHub Copilot CLI vs Paseo
- goose vs Letta
- goose vs Paseo
- Harness² vs Letta
- Harness² vs Paseo
- HarnessRouter vs Letta
- HarnessRouter vs Paseo
- Jules vs Letta
- Jules vs Paseo
- Junie CLI vs Letta
- Junie CLI vs Paseo
- Kilo Code CLI vs Letta
- Kilo Code CLI vs Paseo
- Kimi Code CLI vs Letta
- Kimi Code CLI vs Paseo
- Kiro CLI vs Letta
- Kiro CLI vs Paseo
- Letta vs mini-swe-agent
- Letta vs MiniMax Code
- Letta vs Mistral Vibe CLI
- Letta vs Muse Code
- Letta vs OpenAI Agents API
- Letta vs OpenAI Codex
- Letta vs OpenCode
- Letta vs OpenHands
- Letta vs OpenMausBot
- Letta vs Orca
- Letta vs Prime Agent
- Letta vs Qoder CLI
- Letta vs Qwen Code
- Letta vs Mirror CLI
- Letta vs Rovo Dev CLI
- Letta vs Sculptor
- Letta vs T3 Code
- Letta vs Traycer
- Letta vs Unstoppable
- Letta vs Verdent
- Letta vs Vibe-Trading
- Letta vs Warp (Warp Agent CLI and the Oz Agent API)
- mini-swe-agent vs Paseo
- MiniMax Code vs Paseo
- Mistral Vibe CLI vs Paseo
- Muse Code vs Paseo
- OpenAI Agents API vs Paseo
- OpenAI Codex vs Paseo
- OpenCode vs Paseo
- OpenHands vs Paseo
- Orca vs Paseo
- Paseo vs Prime Agent
- Paseo vs Qoder CLI
- Paseo vs Qwen Code
- Paseo vs Mirror CLI
- Paseo vs Rovo Dev CLI
- Paseo vs Sculptor
- Paseo vs T3 Code
- Paseo vs Traycer
- Paseo vs Unstoppable
- Paseo vs Verdent
- Paseo vs Vibe-Trading
- Paseo vs Warp (Warp Agent CLI and the Oz Agent API)
- Clawboo vs Letta
- Clawboo vs Paseo
- CLI Manager vs Letta
- CLI Manager vs Paseo
- Harness vs Letta
- Harness vs Paseo
- Letta vs Paperclip
- Letta vs Parallax
- OpenMausBot vs Paseo
- Paperclip vs Paseo
- Parallax vs Paseo
Machine-readable
- This page as Markdown
/compare/letta-vs-paseo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/letta.json·/api/v1/tools/paseo.json - From a terminal
anchor compare letta paseo(the CLI) - Over MCP
compare_tools {"a": "letta", "b": "paseo"}at/mcp, no key