Article

How to add ACP coding agents to Vibe Kanban

Vibe Kanban users can check agent compatibility, terminal sign-in, model controls, permission limits and provider costs before starting work.

Editorial illustration for How to add ACP coding agents to Vibe Kanban: a controlled task flows from input to output. Not documentary evidence.

Vibe Kanban 0.1.46, released on 15 November 2026, lets developers and small software teams add compatible coding agents from the ACP registry. Sign in to the chosen agent in a terminal, add it under Settings → Agents → Available agents, then select it for a workspace.

This route supports agents distributed through npx, a package runner supplied with Node.js—not every agent that speaks ACP. The release’s registry filter also keeps existing built-in integrations separate.

1. Check the app, runtime and agent

Agent Client Protocol (ACP) is a common way for coding agents to communicate with an editor or another client. Here, Vibe Kanban is the client; each agent still determines which optional controls it supports.

Confirm that the running Vibe Kanban app is version 0.1.46 before following these steps. Its npm package requires Node.js 20.19.0 or later. You can check the installed runtime with node --version, but also check the chosen agent’s requirements: it may need a newer version.

The ACP registry listed Auggie CLI, Cline, Kilo and Bob with npx distributions on 15 November. These are examples, not a guarantee of successful operation on every machine or account. Agents offered only as downloadable binaries or through the Python runner uvx do not qualify for this release’s installer.

Copilot, Gemini, Qwen, Droid, Claude and Codex are excluded from the available-agent list because Vibe Kanban already integrates them. Keep using those built-in entries rather than looking for a second registry installation.

2. Sign in from a terminal

If the chosen agent needs an account, follow its official terminal login process under the operating-system account and environment that will run Vibe Kanban. Generic registry agents have no in-app Sign in button; an installed profile does not authenticate them.

For example, Auggie’s current quick-start calls for Node.js 22 or later, installs the CLI through npm, then uses auggie login. Follow the provider’s own sign-in flow and confirm your account has the required access. That login command is specific to Auggie, not a universal ACP command.

3. Install it and let the model list refresh

The documented installation route is:

  1. Open Settings → Agents and find Available agents.

  2. Choose Install beside the agent. If settings edits are still unsaved, save or discard those edits first to enable installation.

  3. Select the installed agent in the workspace’s agent picker. Let the model selector finish loading before choosing among its available options.

Keep three checks separate: profile installed, account signed in, session working. The installation step saves a profile. The agent launcher runs its package through npx, which may need to fetch it. Even discovering model options starts an agent process, so a package or sign-in problem can surface before the first task.

The selector can display cached choices while refreshing. A populated dropdown therefore does not prove current access. If it says the agent is not signed in, complete terminal authentication, then reopen the dropdown to retry discovery.

4. Check the permissions actually in effect

Start with Ask, the default for generic registry agents, while checking the setup. The ACP permission controls mean:

  • Ask: permission requests sent through ACP go to you for a decision. It is an approval setting, not a promise that the agent can do nothing without prompting.

  • Auto: Vibe Kanban approves ACP permission requests. Its approval implementation prefers “allow once”, but can choose “allow always” if that is the only allow option. The agent may retain that choice in its own settings.

  • Plan: Vibe Kanban selects the agent’s planning mode when available. If it has none, the configuration logic falls back to Ask, not Auto. Do not treat a saved Plan selection as a universal read-only guarantee.

Choose a supported model, then any reasoning option it exposes. On the first run, read the conversation’s effective configuration summary for the model, reasoning, mode and permissions actually reported. Unavailable model or mode selections and configuration failures can produce warnings while the run continues. A missing reasoning control can be skipped silently; no warning does not prove that a saved choice applied.

If the next step is getting another agent to critique a proposed change, see how to get a second AI opinion on a coding plan in VS Code. That is a separate review workflow, not a feature granted by installing an ACP agent.

5. Budget for the agent, not just the app

Vibe Kanban’s Apache-2.0 application licence is separate from each agent’s licence, account terms and model charges. Registry installation does not create a provider subscription or a shared allowance covering every agent.

For one concrete example, Augment’s current Standard offer lists US$20 a month for up to 50 seats, CLI access and US$20 of pooled monthly usage across language models, Context Engine and compute. Top-ups cost extra; the page lists language-model usage at provider API rates plus a 40% service fee. This is an Augment offer, not a Vibe Kanban fee or a price per task. Confirm eligibility in your own account.

This setup is for local workspaces. In its 10 April 2026 announcement, bloop said it was closing the company, terminating subscriptions and continuing Vibe Kanban as community-maintained open source. The notice said local workspaces would continue; it is not evidence of a current hosted subscription offer.

Local orchestration does not mean offline inference. The cached registry list can survive a connection failure, but downloading an uncached agent package or using a cloud model still needs the relevant network access.

6. Remove an agent before downgrading

To remove an agent, resolve unsaved settings edits and choose another default if necessary: the server blocks uninstalling the current default. Then use Uninstall in the agent list. This removes its Vibe Kanban profile, not necessarily its package cache or provider credentials.

The maintainer’s downgrade guidance says to uninstall registry agents before moving to an older Vibe Kanban version, which cannot read their settings and falls back to defaults. The same guidance says previous conversations remain readable after uninstalling an agent.

For a first task, keep the requested change small and review the code and relevant check results before accepting it. If your next decision is whether to divide work among several agents, when to use Antigravity’s coding-agent teams explains that separate workflow choice.