Codius App

Providers

How Codius thinks about coding agents, wrapping existing CLIs, native vs ACP support, and where to go next.

Codius AppGuide

Codius doesn't ship its own coding agent. It launches and supervises existing agents you've already installed—Claude Code, Codex, OpenCode, Cursor, Gemini, and the rest. Your subscriptions, config, skills, and MCP servers stay intact. Codius adds a visual command center, cross-device control, and orchestration.

If you use a Codius Coding Plan, connect one API key in the App and Codius can supply the provider and default model automatically when it launches a compatible agent. See Codius model access.

Mental model

A provider is the contract between Codius and one external agent CLI: how to launch it, how to stream its output, how to send input back, what modes it supports. The actual binary lives on your machine and runs as a normal subprocess.

Two tiers

  • Native support, Codius ships a bundled adapter for the major agents (Claude Code, Codex, OpenCode, pi). Auto-discovered when the underlying CLI is installed, with mode metadata and voice support where applicable.
  • ACP catalog, any agent speaking the Agent Client Protocol is supported through a generic adapter. Codius ships a curated catalog of one-click installs (Cursor, Gemini, GitHub Copilot, Hermes, Kimi, Qwen Code, and 25+ more), and you can add any other ACP agent yourself.

Either way, you install the underlying CLI. Codius runs it.

Where to go next

  • Supported providers, the full list with install links.
  • Codius model access, connect one key and automatically prepare compatible agent sessions.
  • Custom providers, add your own provider, point an existing one at a different endpoint, run multiple profiles, or override the binary in ~/.codius/config.json.

Last reviewed 2026-07-28 · Capability verified · Public docs are adapted and capability-checked before publication.

Provenance: public-docs/providers.md from CodiusAI/codius-app at 9ab17e8cc8b8.