ACP and the native agent
Dimo talks to an agent over ACP (Agent Client Protocol). Handshake, capability negotiation, session create, turn prompts, and permission requests use that protocol. Dimo is the client on this link. The Agent Runtime is the server.
Login, keys, model catalogs, and native plugins stay in that agent’s official directory. Claude Code uses ~/.claude. Codex uses its own auth.json and config.toml. Dimo may start profile-declared official login, or write fields the profile already names. Native config files remain the Runtime’s persistent authority.
Authority
| Concern | Authority |
|---|---|
| Conversation, turn, permission request, tool-call display | ACP; Dimo as client writes the event log |
| Official login, key files, model vendors | Agent-native config |
| Plan and quota display | Read-only projection; purchase and change happen on the vendor site |
| Local runtime availability | Dimo probe and installation lock |
| Reusable Model Provider presets | Dimo stores intent; Runtime sees them after projection into native config |
| New-session defaults (model, mode) | Dimo global memory; existing conversations keep their config |
When ACP and a local probe can both supply the same status, ACP wins. A built-in profile may offer a local management fallback only when ACP lacks that status. Ordinary registry entries have no dedicated local probe.
Credentials
Auth credentials are held by Agent Runtime config or the user’s external environment. Dimo may start the official account flow, or edit locally declared credential fields. Terminal interaction is not harvested into a second secret store. In-page device authentication exists only for adapted, fixed-endpoint official flows (currently Codex): a short-lived device code may cross IPC; the access token is exchanged in the backend and written straight into the official credential file.
Topology
Local agents split by install shape into native ACP and adapter-backed ACP. See Native ACP and adapter ACP.
Native plugin management
Settings → Agents → the agent’s detail can fold out a native plugin list. It only shows Skill, MCP, Runtime, Hook, and Workflow owned by that agent. Actions depend on a reliable native adapter. Dimo App extension rights stay with Dimo plugin packages.