Extensible harness

Letta Harness

Memory-first harness for persistent agents across machines and sessions.

Status
Active
License
Apache-2.0
Evidence
Documented + code-verifiable, 23 sources
Product record checked
2026-07-27

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

Why it qualifies as a coding harness

This confirms category fit, not product quality. Every required criterion links back to first-party evidence.

Qualifies4 of 4 required criteria evidenced
  • Adaptive agent loop

    Documented

    The system repeatedly observes results and chooses the next action instead of following a fixed one-pass graph.

  • Repository tool execution

    Documented

    The system can use tools to inspect and change a repository or its execution environment.

  • Task-aware context management

    Documented

    The runtime assembles, updates, compacts, retrieves, or persists task-relevant context while work proceeds.

  • Model-independent runtime control

    Documented

    Permissions, budgets, interruption, policy, or stop controls operate outside the model's own text generation.

Membership establishes category fit only. It does not score quality, safety, autonomy, model capability, or benchmark performance. · Read the membership rule.

How it works under the hood

Seven mechanisms mapped from first-party records. These labels describe what the harness provides, not how intelligent its model is.

7/7layers documented
  • Execution & isolationSandbox availableDocumented mechanism, not a performance score.
  • Tooling & integrationsExtensible toolsDocumented mechanism, not a performance score.
  • Context & statePersistent stateDocumented mechanism, not a performance score.
  • Lifecycle & recoveryManaged recoveryDocumented mechanism, not a performance score.
  • ObservabilityLogs/transcriptsDocumented mechanism, not a performance score.
  • VerificationTool-assistedDocumented mechanism, not a performance score.
  • Governance & permissionsPolicy controlsDocumented mechanism, not a performance score.

Public code audit

3/5public artifacts present
Security policy
Not found
CI workflow
Present at inspected commit
Automated tests
Present at inspected commit
Evaluation assets
Not found
Contributor documentation
Present at inspected commit

The v0.29.4 client and harness tree contains 580 test-like files and eleven workflows with contributor documentation but no root security policy or dedicated product-evaluation suite. Managed Letta API, Cloud, and sandbox implementations are outside this client-source audit.

Inspect commit 286a01d10602eab4a356f2b062e817310f992966, checked 2026-07-27

Measured configurations

No benchmark run passes the full metadata admission policy for this harness yet. Missing data is not scored as zero.

Benchmark policy and all runs

Capability support

Documented first-class product support, checked against the sources below.

External tools (MCP)
DocumentedProduct-supported MCP integrationSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Local models
DocumentedLocal or self-hosted model pathSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Agent parallelism
DocumentedDelegated or parallel agent workflowSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Runs without an open UI
DocumentedNon-interactive or automation surfaceSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Browser control
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Isolated execution
Depends on surfaceManaged cloud sandbox; local tools remain host-executedSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Undo file changes
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.

Primary evidence

Each capability claim is tied to a first-party record and a verification date.

Product record checked 2026-07-27
View 15 additional sources
Product and interfaces3 sources
Execution and control1 sources
Automation and extensions6 sources
Enterprise and operations1 sources
Releases and public code audit4 sources