Connect your coding agents
Recoder drives the agent CLIs you already have — Claude Code, Codex, opencode, Cursor, Gemini CLI and more. How detection and auth work.
Recoder drives the agent CLIs you already have installed. It does not bundle or resell them — you keep using each agent exactly as its vendor intended, with your own auth. Recoder detects what's on your PATH and orchestrates them.
How detection works
On launch (and whenever you refresh), Recoder probes your PATH for supported agent CLIs via its /api/conductor/runtimes endpoint. Each agent shows as available (installed + on PATH, auth looks present) or not detected (install it and refresh). Detection is a fresh PATH probe, so if you install an agent while Recoder is open, just refresh — no restart needed. Recoder never fabricates availability.
Supported runtimes
| Runtime | Display name |
|---|---|
claude_code | Claude Code |
codex | Codex |
opencode | opencode |
cursor | Cursor |
gemini_cli | Gemini CLI |
qwen_code | Qwen Code |
crush | Crush |
pi | pi |
recoder_code | Recoder Code |
The list you actually see is whatever is installed on your machine.
The setup pattern (every agent)
Install its CLI, authenticate it the way you normally would, make sure it's on your PATH, then refresh Recoder. For example:
claude --version # Claude Code
codex --version # Codex
opencode --version # opencode- •Claude Code — authenticate via Anthropic's interactive login, or an ANTHROPIC_API_KEY in your environment.
- •Codex — authenticate via its login flow, or an OPENAI_API_KEY in your environment.
- •opencode — configure its provider/key as you normally would.
- •Cursor, Gemini CLI, Qwen Code, Crush, pi — same recipe: install, authenticate, ensure it's on PATH, refresh.
Recoder inherits your shell environment, so agents pick up the same provider keys and config they use when you run them directly. Recoder does not intercept, proxy, or resell those tokens.