Back to Documentation
AMADEV Docs
Configuration

Providers

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

#Providers

# Amadev doesn't ship its own coding agent. It launches and supervises existing CLIs you've already installed and authenticated, Claude Code, Codex, OpenCode, Cursor, Gemini, and the rest. Your subscriptions, your config, your skills, your MCP servers all stay intact. Amadev just gives you a UI, a CLI, a relay, and orchestration on top.

#Mental model

# A provider is the contract between Amadev 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, Amadev 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. Amadev 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. Agent Client Protocol Either way, you install the underlying CLI. Amadev runs it.

#Where to go next

#

Code
~/.amadev/config.json

amadev.org/agents View this page on GitHub