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.

`opencode export` and `opencode import` move single sessions as JSON with one command each, but moving the whole agent (config dir, instructions, skills, credentials, database) means copying documented directories by hand. Export is available immediately. 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.

All state is local, so nothing stays with the provider, and MCP OAuth uses dynamic client registration. However, the documented session export carries file-snapshot history only as hash references to a separate internal git store. The documented storage layout is also out of date (it describes per-project JSON storage, while the code uses opencode.db). 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 runtime is MIT-licensed with no licence check. The model catalogue fetch from models.opencode.ai times out and falls back to a cache or bundled snapshot, and can be pointed elsewhere or disabled (OPENCODE_MODELS_URL, OPENCODE_DISABLE_MODELS_FETCH). Update checks can be disabled. Needs hands-on confirmation with provider domains blocked. 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.

Tools run in the runtime, and any AI SDK or OpenAI-compatible provider can be configured, including documented local servers (Ollama, llama.cpp, LM Studio). Web search, on by default only with the provider's own models, can be turned on for any model with documented OPENCODE_ENABLE_EXA / OPENCODE_ENABLE_PARALLEL flags. The docs say the core workflow relies on tool calling. 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.

Sessions, config, credentials and snapshots live on the owner's machine (~/.local/share/opencode, ~/.config/opencode), 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