Agent configuration

How Kanban detects, selects, and launches CLI agents for your tasks.

Kanban is agent-agnostic. It auto-detects which CLI agents are installed on your system and lets you choose which one to use globally or per task.

Agent detection

When Kanban starts, it scans your PATH for known agent binaries. Only agents whose binary is found are shown in the agent selector. No manual registration is required — install an agent globally and Kanban picks it up on the next launch.

On first launch with no saved config, Kanban automatically selects the best available installed agent in priority order: claude first, then codex. If neither is installed, cline is used as the default.

Default agent

Set your default agent in Settings → Agent. Every new task card uses this agent unless you override it. Changing the default does not affect tasks that are already running.

Per-task agent

You can assign a different agent to any individual task from the task form when creating or editing a card. The per-task setting takes precedence over the global default.

Supported agents

The table below lists every agent in the catalog. The Autonomous flags column shows the arguments Kanban appends when autonomous mode is enabled, allowing the agent to run without prompting for permission on each action.

Only cline, claude, and codex currently support full autonomous launch. The remaining agents appear in the catalog but launch support is not yet enabled.

Agent	ID	Binary	Autonomous flags
Cline	cline	cline	--auto-approve-all
Claude Code	claude	claude	--dangerously-skip-permissions
OpenAI Codex	codex	codex	--dangerously-bypass-approvals-and-sandbox
OpenCode	opencode	opencode	(none)
Droid CLI	droid	droid	--auto high
Gemini CLI	gemini	gemini	--yolo

Autonomous flags bypass the agent’s normal permission prompts. Kanban passes these flags only when you have enabled autonomous mode for a task. Review what each flag does in the agent’s own documentation before enabling autonomous mode.

Autonomous mode

Autonomous mode is enabled by default. When it is on, Kanban appends the agent’s autonomous flags to every task launch so the agent can complete work without interrupting you for approvals. You can toggle this in Settings.

Cline settings

Cline uses a native SDK integration inside Kanban rather than being launched as an external CLI process. This means several settings that other agents expose via flags are instead configured through the Cline section of Settings:

Provider & API keys

Select your LLM provider and enter API credentials directly in Settings → Cline. Kanban delegates authentication entirely to the Cline SDK.

Model selection

Choose which model Cline uses for tasks. Available models are populated by the Cline SDK based on your selected provider.

OAuth login

If your provider supports OAuth, log in from the Cline settings section. Kanban does not manage OAuth tokens directly — the Cline SDK handles session persistence.

Reasoning settings

Configure reasoning budget and related options from the Cline section. These settings are sourced from the Cline SDK and vary by model.

All other Kanban settings — default agent selection, autonomous mode, prompt templates, and shortcuts — apply to Cline the same as any other agent.