Head to head · Agent harnesses · October 2026 research run

Letta vs Orca

Letta scores 59.7 (C) on agent readiness against Orca's 57.4 (C), and leads in 4 of 7 scored categories. Orca leads on security & auth. 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 40
  • 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

Orca C

Best for Developers who want an orchestrator agent to split work across parallel coding agents, on desktop or mobile.

Ahead on

  • Security & auth, 43 against 35

Also in its favour

  • No key needed to call it

Watch for

Anonymous usage data collected by default, with an opt-out

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 +20

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.

Orca 40

Scored on the cloud option. No protocol (0). The cloud price wasn't found on the pages read (0). The desktop app is free and MIT with no card (20). The local app needs no sign-up that we found (20). 0 + 0 + 20 + 20 = 40.

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.

Orca 75

Tags to v1.4.251 and commits on 6 November 2026 (30). Many 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). Extensive CI (10). 30 + 20 + 0 + 15 + 10 = 75.

Security & auth Orca +8

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.

Orca 43

Harness reading. Anonymous usage data with an opt-out, per the README's link to its telemetry docs (15 of 30). Worktrees per agent and a sandboxed Linux build (12 of 20). No prompt-injection guidance (5). No audit log (5). A dependency-security workflow (6 of 20). 15 + 12 + 5 + 5 + 6 = 43.

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.

Orca 65

Harness reading. A docs site with CLI orchestration and native chat pages (65).

Score by category

CategoryWeight this runLettaOrcaEdge
Reliability16%205858even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27065Letta +5
Agent ergonomics13%16.26770Orca +3
Security & auth14%17.53543Orca +8
Payments & pricing10%12.56040Letta +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88575Letta +10
Transparency & trust7%8.85554Letta +1
Negative events≤1500
TotalC 59.7/100C 57.4/100

Facts side by side

FactLettaOrca
KindAgent harnessAgent harness
VendorLettaLovecast Inc.
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthOAuth or keyNone
PricingFreemiumFree
x402nono
LicenceApache-2.0MIT
Read-only variant documentednono
llms.txtyesno
Last release2026-11-062026-11-06
Terms last updatedno date givenno document linked
Privacy policy last updatedno date givenno document linked
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waiveryesnot read yet
Popularity3.8k stars, 86k npm/wk, 2.2k PyPI/wknone

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.

Orca

An open-source orchestrator for coding agents with worker agents in their own worktrees, chat and terminal views, a browser and a CLI, on desktop and mobile, with heavy test automation. It collects anonymous usage data by default, and the cloud option's pricing wasn't found.

Before you call either

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

Orca

  1. See the telemetry docs on onorca.dev to opt out of anonymous usage data
  2. Use the orchestration CLI to hand a large task to one agent that starts workers

Questions

Which is better for AI agents, Letta or Orca?

Letta scores 59.7 (C) on agent readiness against Orca's 57.4 (C), and leads in 4 of 7 scored categories. Orca leads on security & auth.

Are Letta and Orca open source?

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

Other comparisons with Letta or Orca

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.