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.

The only documented exports are chat logs (CSV/JSON/JSONL) and per-chat exports. Desktop documentation gives the storage folder location but no documented backup, export, import or migration procedure for the whole instance or a workspace, so there is no documented export of the agent. 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.

The default export route covers conversation text only. Configuration, prompts, memories, custom skills, flows, scheduled jobs, documents, embeddings and integration settings are not in any export; they remain only in the local storage folder. 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.

The free Desktop app needs no account or licence check, and the self-hosted terms say it needs no connection to Mintplex servers (the embedder has a Hugging Face primary source with a Mintplex CDN fallback). However, the Desktop Terms of Use grant only a non-exclusive, non-transferable licence that they do not state is perpetual or irrevocable, so public evidence does not establish an irrevocable right to run the distributed Desktop binary (G12). The MIT server core offers another route, but no documented migration path onto it exists. 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.

The default LLM is a built-in local engine (Ollama). Many local providers are supported (Ollama, LM Studio, LocalAI, etc.), and so are local embedders, speech-to-text, text-to-speech and image generators (Ollama, LocalAI, Lemonade). Agent tools run in the runtime, and an 'UnTooled' prompt-based fallback covers models without native tool calling. The only model-locked feature found is a beta-preview computer-use feature fixed to an Anthropic model, which is not part of the evaluated default. 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.

Desktop needs no account. All state (anythingllm.db, documents, vector DB, plugins, .env) lives in a local storage folder on the owner's device, so a current copy is always in the owner's hands whatever happens to the provider. 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