Compatible coding agents
Choose a built-in adapter or register a local command that edits a Git worktree.
Each paired runner advertises the agents available on that machine. Choose a repository to see its runner’s list in the task composer. Each built-in adapter probes its own CLI. OpenCode reports whether it has a credential saved. Expired keys can still appear in that inventory. If a run reports expiry, replace the key locally and retry the card. One ready agent is sufficient.
| Adapter | Authenticate on the machine |
|---|---|
| Claude Code | claude auth login |
| Codex | codex login |
| Kiro CLI | kiro-cli login |
| OpenCode | opencode auth login |
Each CLI uses its own account and model configuration. You can select a model when starting the runner with AK_CLAUDE_MODEL, AK_CODEX_MODEL, AK_KIRO_MODEL or AK_OPENCODE_MODEL. The task records the selected model when supplied.
Connect another CLI
A compatible CLI runs unattended, accepts a task through an argument or standard input, edits files in its current directory, and exits when finished. The runner captures plain-text output and runs the repository’s acceptance command separately. Interactive-only clients need a noninteractive command before they can work here.
Create ~/.agent-kanban-runner/agents.json on the paired machine. If you set AK_RUNNER_HOME, place the file in that directory. The example assumes you installed a command named my-agent whose run subcommand accepts a prompt argument. Replace those values with your CLI’s documented invocation.
[
{
"id": "my-agent",
"label": "My local agent",
"command": "my-agent",
"args": ["run", "{prompt}"],
"promptVia": "arg",
"efforts": []
}
]
For a CLI that reads a prompt from stdin, use "promptVia": "stdin" and omit {prompt} from the arguments. The runner passes each argument directly to the executable. Keep account credentials in the CLI’s own local configuration.
Restart the runner with agent-kanban start. To load a file from another location, use AK_RUNNER_AGENTS=/absolute/path/agents.json agent-kanban start. A configured CLI appears by its label in the composer, board and review. Its executable is detected, and its login remains unprobed. Run the CLI’s own sign-in command locally before submitting work.