Compare agents

An owner without developer skills can export the agent and restore it working on a runtime or host the provider does not operate, within minutes of asking and without provider approval. Running the runtime on the owner's own machine counts as not provider-operated.

AgentFile (.af) export/import has been removed from Letta Code, and no command moves a Cloud agent to local mode or a self-hosted runtime. Letta's docs say the legacy API export cannot be imported by the local backend or a self-hosted App Server, so restore works only on provider-operated systems. Sources

Export is immediate (the agent is one .adf file; copying it and using Open is documented), but restoring a working agent on another machine takes several documented steps: import the owner seed phrase to unlock sealed keys, re-add a model provider key (app-level keys are not in the file), re-register app-level MCP servers, then review and accept the file. One shortfall (restore is not a single action). Sources

The export contains everything that defines the agent: configuration, instructions, memory, action history, logic, schedules and triggers, files, any identity, and credentials or a way to re-link each integration without any provider-registered client or broker. Derived data (embeddings, indexes, summaries) is accompanied by the source it was derived from.

Only memory (a MemFS directory copy) and a plain-text conversation transcript can be exported; the transcript is marked truncated past 200 pages. The system prompt, model, tool and permission config, Cloud schedules (held in Letta's cloud-api database), server-held secrets and the agent identity stay with the provider. Sources

The spec places config, instructions, memory, loops, timers, triggers, lambdas, files, messages, audit, logs, sealed identity keys and per-agent credentials in the .adf file; the project holds nothing. Items outside the file (app-level provider keys, app-scoped MCP credentials, WhatsApp session directory, runtime settings) can be re-linked by the owner without any ADF-registered client (MCP OAuth uses dynamic client registration; subscriptions use OpenAI/xAI client ids). A customised global base prompt is an app setting and does not travel; recorded, not counted, because the default install uses the shipped prompt. Sources

With a non-provider model configured per P4, the exported agent runs indefinitely without any service, account, licence or payment controlled by the original provider, and the owner holds a perpetual, irrevocable right to run it. No provider action, inaction or disappearance can disable or degrade it.

In the default offering the agent's state lives on Letta Cloud, and the CLI needs a Letta account or token to start a Cloud agent. There is no exported form that runs without the provider. Local mode is Apache-2.0 and needs no account, but a Cloud agent cannot be moved into it. Sources

The runtime is MIT-licensed with no licence check, account or ADF-run relay; the only ADF-project endpoints (GitHub update check, MCP registry, skill catalog, online docs) are optional, have off switches or bundled fallbacks, and are not needed to start or act. Mesh uses LAN, tailnet or owner-chosen addresses. Desk grade; a provider-blocked run is required at certification. Sources

The owner can choose any model that meets a documented minimum, including a local open-weight model, without provider involvement, and every capability of the agent (tools, triggers, messaging, memory, automation) keeps working. A swap may lower reasoning quality but never removes a capability.

Owners can bring their own keys, and /connect offers Ollama, LM Studio, llama.cpp and any OpenAI-compatible endpoint. However, no minimum model contract is documented. Defaults point to hosted routes: the compaction model is letta/auto and the title model is openai/gpt-6-luna. Full capability with a local open-weight model is therefore not established. Sources

Tool calling is the documented minimum and local open-weight models (Ollama, LM Studio, vLLM, llama.cpp) are first-class provider options; triggers, timers, lambdas and middleware run in the runtime. However, video input is implemented by injecting OpenAI-format video_url parts and is documented only for hosted providers (OpenRouter, Gemini), and no test against a local model is published, so under G12 at least one capability is not shown to survive a local model. Sources

Whatever the P2 export contains stays obtainable, current to the moment of termination, after account suspension or ban, a lapsed subscription, a price change, an acquisition, or the provider shutting down.

The terms reserve the right to 'suspend or end the Services at any time at our discretion and without notice'. They include no post-termination export window and no shutdown plan. Apart from a locally synced copy of memory, termination ends access to the Cloud-held state, and mirroring memory to an owner-held repository is off by default. Sources

State is local-first: the agent is a SQLite file on the owner's disk with no ADF account or hosted copy, so no termination, ban or shutdown by the project can remove access to it. Sources