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.

Gemini CLI ships no export/import for the agent and no documented procedure for moving it; the only export command, /chat share, exports a single conversation as Markdown/JSON. Agent state sits in local directories (~/.gemini, project .gemini) documented piecemeal, so moving it is an undocumented manual copy that also needs auth re-setup. 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 agent-defining state is local: settings, GEMINI.md memory, skills, policies, extensions and JSONL session records. Nothing agent-defining is held server-side. Re-linking the default model integration ('Sign in with Google') needs Google's own registered OAuth client, and credentials default to the OS keychain rather than the ~/.gemini directory. 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 Apache-2.0 and the source contains no licence check or expiry. Experiment flags are fetched only when a Code Assist server is in use, and usage-statistics failures are non-fatal. Whether every capability survives with all Google domains blocked has no public documentation (hands-on test), so the pass is withheld under G12. 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 documented model choices are Gemini models only (Auto, Pro, Flash). Other or local models can be reached only by pointing the documented GOOGLE_GEMINI_BASE_URL override (localhost allowed) at a third-party Gemini-API-compatible proxy, which is a workaround. The local Gemma support is an experimental routing classifier, not the agent model. The built-in Google Search grounding tool depends on a Gemini hosted-model feature. 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.

Agent state (config, memory, skills, session records) is stored on the owner's machine by default, so a current copy stays in the owner's hands if the Google account or licence is terminated or the service shuts down. 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