Agent adapters
OpenDesign generates nothing itself. The agent you connect does the work. This page is for choosing one.
What an adapter is
Each adapter is a thin shim translating one agent's native message format into OpenDesign's skill protocol. Adding a new agent is a single file, not a fork.
The consequence is that skills and design systems are agent-agnostic. Switching agents is a config line, not a redesign.
The 21
| Agent | Vendor | Credential |
|---|---|---|
| Claude Code | Anthropic | Anthropic API key (BYOK) or Claude subscription |
| Codex | OpenAI | OpenAI API key (BYOK) or ChatGPT subscription |
| Cursor Agent | Cursor | Cursor account (uses your provider keys) |
| Gemini CLI | Google AI Studio key (BYOK) | |
| GitHub Copilot CLI | GitHub | GitHub Copilot subscription |
| OpenCode | community | Provider keys via OpenCode config (BYOK) |
| Qwen Code | Alibaba | DashScope / Qwen API key (BYOK) |
| Grok Build | xAI | xAI SuperGrok OAuth (grok login --oauth) |
| Hermes | community | xAI / OpenAI / Anthropic keys via hermes auth add |
| Kimi CLI | Moonshot | Moonshot API key (BYOK) |
| Devin for Terminal | Cognition | Devin account |
| DeepSeek TUI | DeepSeek | DeepSeek API key (BYOK) |
| Pi | community | Provider keys (BYOK) or subscription login |
| Mistral Vibe CLI | Mistral | Mistral API key (BYOK) |
| Kiro CLI | Amazon (preview) | AWS credentials (BYOK) |
| Kilo | community | Provider keys via Kilo config (BYOK) |
| Qoder CLI | Alibaba | Qoder account (qodercli login) |
| Trae CLI | ByteDance | Provider keys (BYOK) |
| Aider | community | Provider API keys (BYOK) |
| Antigravity | Google account (preview) | |
| DeepSeek Reasonix | community | DeepSeek API key (BYOK) |
DeepSeek Harness (dsh) is listed separately: it can already build and edit interfaces in a real repository, and connecting it to OpenDesign guides that work with design systems, reusable skills, and local artifact previews.
The counts don't match, and that's fine
The official FAQ says 17 first-party BYOK adapters; the agents page lists 21 entries. The list is growing and the two pages update on different schedules. open-design.ai/agents is the source of truth.
Choosing
| Your situation | Start with |
|---|---|
| Already paying for Claude | Claude Code |
| Already paying for ChatGPT | Codex |
| Using Cursor | Cursor Agent |
| Have GitHub Copilot | GitHub Copilot CLI |
| Want the cheapest trial | Gemini CLI or Qwen Code |
| Work approved one vendor | That vendor's adapter |
Look at what you already pay for before you optimise for model quality. Design work and coding work draw on the same pool, which is the most concrete saving here.
Where credentials live
Two places:
.od/media-config.json project credential file
environment variables your shell profileCalls go from your machine straight to the provider. OpenDesign doesn't proxy them. The bill lands on your account there.
Don't commit .od/media-config.json
It holds credentials. Confirm it's in .gitignore before you start.
Connecting without exposing a key
If Claude Code, Codex, Cursor, or OpenCode is installed and signed in, point OpenDesign at it. The desktop build scans your PATH.
Connected this way, no key is ever handed over — generation uses the credentials that CLI already holds, and nothing leaves your machine. Community walkthroughs keep singling this out as the project's strongest security property.
What BYOK means here
- Credentials live in
.od/media-config.jsonor your shell environment. - API calls go from your machine directly to your provider.
- Switching providers is a key swap, not a re-onboard.
- API spend bills to your account with each provider.
What switching costs
| Thing | Bound to the agent? |
|---|---|
Skills (SKILL.md) | No — plain Markdown |
Design systems (DESIGN.md) | No |
| Generated artifacts | No — files in your repo |
| Credentials | Yes, one set per provider |
Related
- Get started / Connect your agent
- Official page: open-design.ai/agents