At a glance
The stateful open-source harness formerly called Letta Code, with git-backed self-editing memory, skills, MCP connectivity, trusted runtime mods, foreground or background subagents, headless execution, schedules, multi-provider access, and selectable local, remote, or managed cloud environments.
Good choice if
- Long-lived agents that should remember preferences, prior work, and learned skills
- Multi-agent workflows routed across laptops, remote machines, CI, and managed cloud sandboxes
- Developers combining subscriptions, BYOK providers, local runtimes, MCP, schedules, and messaging surfaces
Check before choosing
- Its persistent-memory model is more complex than a disposable repository session
- The interactive CLI currently starts in unrestricted mode; approval prompts require standard mode or explicit persistent policy rules
- Local client tools execute with the selected computer's shell, files, credentials, and installed software even when agent state lives in Letta Cloud
See 3 more considerations
- Managed sandboxing is an optional execution target, not the default boundary for local CLI work
- The platform supports external MCP tools, but current first-party guidance recommends skills instead of MCP for the Letta app and CLI; external servers remain separate execution and trust boundaries
- Mods execute as fully trusted code inside the harness process and can add tools, commands, hooks, permission policies, UI, and model providers, so they are not a sandboxed extension mechanism
