Head to head · Agent harnesses · October 2026 research run
Letta vs Traycer
Letta scores 59.7 (C) on agent readiness against Traycer's 57 (C), and leads in 4 of 7 scored categories. Traycer leads on reliability, security & auth and transparency & trust. 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
- Schema & documentation, 70 against 65
- Payments & pricing, 60 against 30
- 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
Traycer C
Best for Teams who want several coding agents working together with shared context and boards.
Ahead on
- Reliability, 65 against 58
- Security & auth, 42 against 35
- Transparency & trust, 60 against 55
Also in its favour
- No key needed to call it
Watch for
Privacy Mode is opt-in for individuals; with it off, prompts may be logged
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.
Payments & pricing Letta +30
Letta 60
No x402, MPP or L402 (0 of 40). Per-unit API prices are public, $0.10 per active agent a month and $0.00015 a second of tool execution, plus plan prices (20). A $0 plan with bring-your-own keys; no card is mentioned (20). The CLI runs locally without signing in (20). Total 60.
Traycer 30
Scored on the paid option, Traycer's own inference subscription, whose price wasn't read (0 of 20). No protocol (0). Bring-your-own-agent use is free (20). Accounts for sync and teams weren't checked, half (10). 0 + 0 + 20 + 10 = 30.
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.
Traycer 75
Commits on 6 November 2026 and host 1.5.3 (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 apps and CLI packages (15). CI with tests (10). 30 + 20 + 0 + 15 + 10 = 75.
Reliability Traycer +7
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.
Traycer 65
Local software. Builds for macOS, Linux and Windows, and package-manager publishing workflows (20). test.yml, CodeQL, OpenSSF Scorecard and secret scanning run 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). Host 1.5.3 (15). 20 + 15 + 0 + 15 + 15 = 65.
Security & auth Traycer +7
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.
Traycer 42
Harness reading. Code is processed in memory and not used for training, but Privacy Mode is opt-in for individuals, prompts may be logged with it off, and Sentry and PostHog 'may be enabled in release builds' (10 of 30). No approval model described in the README (8 of 20). No prompt-injection guidance (5). No audit log found (5). SECURITY.md, CodeQL, Scorecard and secret scanning (14 of 20). 10 + 8 + 5 + 5 + 14 = 42.
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.
Traycer 65
Harness reading. Mintlify docs, a protocol package and a CLI (65).
Transparency & trust Traycer +5
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.
Traycer 60
MIT (30). README privacy section and a linked privacy policy (not read) (18 of 30). CHANGELOG.md, no deprecation policy (10). Analytics described as 'may be enabled', with no opt-out given in the README (8 of 20). 30 + 18 + 10 + 8 = 66.
Score by category
| Category | Weight this run | Letta | Traycer | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 58 | 65 | Traycer +7 |
| 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 | 65 | Letta +2 |
| Security & auth | 14%17.5 | 35 | 42 | Traycer +7 |
| Payments & pricing | 10%12.5 | 60 | 30 | Letta +30 |
| 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 | 60 | Traycer +5 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 59.7/100 | C 57/100 |
Facts side by side
| Fact | Letta | Traycer |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Letta | Traycer AI |
| 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 | MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-11-06 | 2026-11-06 |
| 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.
Traycer
An open-source app for running several coding agents together with shared context, agent-to-agent messaging and team boards, on every desktop OS. Privacy Mode is opt-in for individuals, and the README says Sentry and PostHog may be on in release builds.
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
Traycer
- Turn on Privacy Mode if you're an individual user and don't want prompts logged
- CLI agents you configure send requests straight to their provider; Traycer's own inference goes through Traycer
Questions
Which is better for AI agents, Letta or Traycer?
Letta scores 59.7 (C) on agent readiness against Traycer's 57 (C), and leads in 4 of 7 scored categories. Traycer leads on reliability, security & auth and transparency & trust.
Are Letta and Traycer open source?
Yes. Letta is open source (Apache-2.0). Traycer is open source (MIT).
Other comparisons with Letta or Traycer
- Agent Zero vs Letta
- Agent Zero vs Traycer
- Aider vs Letta
- Aider vs Traycer
- Amp vs Letta
- Amp vs Traycer
- Antigravity CLI vs Letta
- Antigravity CLI vs Traycer
- Auggie CLI vs Letta
- Auggie CLI vs Traycer
- AXLR vs Letta
- AXLR vs Traycer
- Claude Code vs Letta
- Claude Code vs Traycer
- Cline vs Letta
- Cline vs Traycer
- Conductor vs Letta
- Conductor vs Traycer
- Crush vs Letta
- Crush vs Traycer
- Cursor CLI vs Letta
- Cursor CLI vs Traycer
- DeepSeek Harness (dsh) vs Letta
- DeepSeek Harness (dsh) vs Traycer
- dsh-superagent (DeepSeek) vs Letta
- dsh-superagent (DeepSeek) vs Traycer
- Devin vs Letta
- Devin vs Traycer
- Droid CLI vs Letta
- Droid CLI vs Traycer
- Pi vs Letta
- Pi vs Traycer
- Emdash vs Letta
- Emdash vs Traycer
- Gemini CLI vs Letta
- Gemini CLI vs Traycer
- GitHub Copilot CLI vs Letta
- GitHub Copilot CLI vs Traycer
- goose vs Letta
- goose vs Traycer
- Harness² vs Letta
- Harness² vs Traycer
- HarnessRouter vs Letta
- HarnessRouter vs Traycer
- Jules vs Letta
- Jules vs Traycer
- Junie CLI vs Letta
- Junie CLI vs Traycer
- Kilo Code CLI vs Letta
- Kilo Code CLI vs Traycer
- Kimi Code CLI vs Letta
- Kimi Code CLI vs Traycer
- Kiro CLI vs Letta
- Kiro CLI vs Traycer
- 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 Paseo
- 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 Unstoppable
- Letta vs Verdent
- Letta vs Vibe-Trading
- Letta vs Warp (Warp Agent CLI and the Oz Agent API)
- mini-swe-agent vs Traycer
- MiniMax Code vs Traycer
- Mistral Vibe CLI vs Traycer
- Muse Code vs Traycer
- OpenAI Agents API vs Traycer
- OpenAI Codex vs Traycer
- OpenCode vs Traycer
- OpenHands vs Traycer
- Orca vs Traycer
- Paseo vs Traycer
- Prime Agent vs Traycer
- Qoder CLI vs Traycer
- Qwen Code vs Traycer
- Mirror CLI vs Traycer
- Rovo Dev CLI vs Traycer
- Sculptor vs Traycer
- T3 Code vs Traycer
- Traycer vs Unstoppable
- Traycer vs Verdent
- Traycer vs Vibe-Trading
- Traycer vs Warp (Warp Agent CLI and the Oz Agent API)
- Clawboo vs Letta
- Clawboo vs Traycer
- CLI Manager vs Letta
- CLI Manager vs Traycer
- Harness vs Letta
- Harness vs Traycer
- Letta vs Paperclip
- Letta vs Parallax
- OpenMausBot vs Traycer
- Paperclip vs Traycer
- Parallax vs Traycer
Machine-readable
- This page as Markdown
/compare/letta-vs-traycer.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/letta.json·/api/v1/tools/traycer.json - From a terminal
anchor compare letta traycer(the CLI) - Over MCP
compare_tools {"a": "letta", "b": "traycer"}at/mcp, no key