Open Orchestrators
Back to directory
Vibe Kanban logo

Player profile

Vibe Kanban

An open-source Kanban workspace for planning, running, reviewing, and shipping parallel coding-agent work.

25.2k GitHub stars
Vibe Kanban public platform context screenshot
Public Vibe Kanban context captured from Vibe Kanban website. Vibe Kanban website

Profile

Where it fits

Vibe Kanban is an Apache-2.0 open-source workspace for teams and individuals running coding agents such as Claude Code, Codex, Gemini CLI, GitHub Copilot, Amp, Cursor, OpenCode, Droid, CCR, and Qwen Code.

Its workflow starts from Kanban issues, then creates workspaces where agents get a branch, terminal, and dev server. Operators can review diffs, leave inline comments, preview the app in a built-in browser, open pull requests, and merge finished work.

It belongs in Open Orchestrators because the product focuses on the human planning and review layer around parallel coding agents rather than a single chat session or editor extension.

Builder web analytics

Measure projects built with Vibe Kanban

Vibe Kanban helps builders plan, run, review, and ship coding-agent work. Agent Analytics gives the follow-up agent visitor, source, funnel, and conversion data after those changes reach users.

Install Agent Analytics on the surfaces Vibe Kanban helps ship. The useful loop starts after the agent-built change lands: a later agent can fetch the measured user outcome and decide what to improve next.

First loop to measure

  1. a builder uses Vibe Kanban to plan an issue and run one or more coding agents in workspaces
  2. the selected branch ships to the website, docs, app, onboarding path, demo, or product surface
  3. the changed surface reports visits, sources, CTA clicks, signup, activation, retention, funnels, and experiment events to Agent Analytics
  4. a follow-up agent fetches the Agent Analytics results and turns user behavior into the next issue, review comment, or experiment

Copyable prompt

Use Agent Analytics for this project. If event reporting is missing, add the tracker and report events for this project surface, including Vibe Kanban-built page, traffic source, CTA click, signup, activation event, funnel step, experiment, or shipped branch. Verify events are arriving. Then fetch the last 7 days and compare them with the prior 7 days. Tell me which Vibe Kanban-built page, traffic source, CTA click, signup, activation event, funnel step, experiment, or shipped branch moved users toward value, where users dropped off, which sources mattered, and what my agent workflow should improve next.
Vibe Kanban public platform context screenshot
Public Vibe Kanban context captured from Vibe Kanban website. Vibe Kanban website

Related

More on Vibe Kanban