🎉 v0.0.143 out now - released 2 days ago!💫 "Biggest increase in productivity since Cursor" - Luke Harries✨ Use session IDs for scratches and queued messages (Vibe Kanban) by @LSRCT in https://github.com/BloopAI/vibe-kanban/pull/1613🎉 v0.0.143 out now - released 2 days ago!✨ Make file name in diffs sticky (vibe-kanban) by @anastasiya1155 in https://github.com/BloopAI/vibe-kanban/pull/1631✨ feat: dynamically determine devserver hostname from browser location … by @gsxdsm in https://github.com/BloopAI/vibe-kanban/pull/1640✨ Fix local build for macOS e2e testing (Vibe Kanban) by @stunningpixels in https://github.com/BloopAI/vibe-kanban/pull/1679🎉 v0.0.143 out now - released 2 days ago!✨ @gsxdsm made their first contribution in https://github.com/BloopAI/vibe-kanban/pull/1640🚀 "This project is underrated. I've found it to be useful and fun" - Hamel Husain🔥 Latest features available in v0.0.143🎉 v0.0.143 out now - released 2 days ago!⭐ Star us on GitHub to stay updated💫 "Biggest increase in productivity since Cursor" - Luke Harries✨ Use session IDs for scratches and queued messages (Vibe Kanban) by @LSRCT in https://github.com/BloopAI/vibe-kanban/pull/1613🎉 v0.0.143 out now - released 2 days ago!✨ Make file name in diffs sticky (vibe-kanban) by @anastasiya1155 in https://github.com/BloopAI/vibe-kanban/pull/1631✨ feat: dynamically determine devserver hostname from browser location … by @gsxdsm in https://github.com/BloopAI/vibe-kanban/pull/1640✨ Fix local build for macOS e2e testing (Vibe Kanban) by @stunningpixels in https://github.com/BloopAI/vibe-kanban/pull/1679🎉 v0.0.143 out now - released 2 days ago!
Upcoming Event
Ultimate Agents Hackathon
Sat, Oct 25 • 9 AM–9 PM ET•Betaworks NYC•$5k+ prizes
Move faster withClaude CodeMove faster withClaude Code
Move faster with
Claude Code
Vibe Kanban lets you run coding agents in parallel without conflicts, and perform code review through our diff tool. Now you can focus on planning and quality instead of watching terminal logs.
Install Node.js 18+ then run:
$npx vibe-kanban
Vibe kanban is the biggest increase I've had in productivity since cursor.
Luke Harries
Growth Lead at Eleven Labs
Choose Your Coding Agent
Works seamlessly with all your favorite AI coding agents.
Run local coding agents in parallel
Instead of staring at coding agent logs you can focus on planning and reviewing work while your coding agents work in the background.
Give agents their own workspace
Agents work in separate branches and workspaces on your machine (powered by git worktrees), so they never step on each other's toes during parallel execution. Safely merge changes back when tasks complete.
Review agent changes like human code
Built-in diffs let you inspect, edit, and approve agent work just like any pull request.
Stay ahead of the curve
Thousands of top developers use Vibe Kanban daily to orchestrate AI coding agents
gsxdsm/vibe-kanban
3d
After a commit to the release branch, do a prod build (vibe-kanban)
Run the local build and update script with a git hook if possible. Don't rely on GitHub
gsxdsm
Contributor
merged
impactaky/shelffiles
3d
Move package.nix to example (vibe-kanban)
/openspec:proposal
Move package.nix to examples directory to avoid conflict with user change.
Instead, we should add instruction in README
impactaky
Contributor
merged
0xtsotsi/DevFlow
4d
M3-T3: Merge Gatekeeper with Human-in-the-Loop (vibe-kanban)
**Priority**: MEDIUM (enables safe auto-merge)
**Estimated**: 1 day
Create service that monitors PR status and notifies human for merge approval.
**⚠️ CRITICAL: FORK SAFETY**
- DevFlow is a fork of automaker
- origin = `0xtsotsi/DevFlow` ← **ALWAYS work here**
- upstream = `AutoMaker-Org/automaker` ← Read-only
- NEVER merge to automaker/upstream
**Files to Create:**
- `apps/server/src/services/merge-gatekeeper.ts`
- `apps/server/src/routes/github/routes/merge-request.ts`
**Implementation Details:**
```typescript
const DEVFLOW_REPO = "0xtsotsi/DevFlow";
interface MergeEligibility {
prNumber: number;
repository: string; // ⚠️ MUST validate = DEVFLOW_REPO
isEligible: boolean;
checks: {
ciPassed: boolean;
noComments: boolean;
noRequestedChanges: boolean;
approvals: number;
requiredApprovals: number;
};
}
interface MergeRequest {
prNumber: number;
repository: string;
requestedBy: string;
requestedAt: string;
status: 'pending' | 'approved' | 'rejected';
}
```
**Features:**
- Monitor PR status (CI checks, comments, approvals)
- **Repo validation**: Only process PRs from `0xtsotsi/DevFlow`
- When PR is "ready", notify human via:
- Desktop notification (Electron)
- Vibe Kanban task status change
- Human approves merge → auto-merge to DevFlow main
- Track merge metrics
**Acceptance Criteria:**
- [ ] Polls PR status every 30s when in "review" state
- [ ] Validates PR is from `0xtsotsi/DevFlow` repo
- [ ] Checks CI status, comment count, approval count
- [ ] Creates "ready for merge" task when all checks pass
- [ ] Auto-merges to DevFlow main on human approval
- [ ] Posts merge summary to PR
- [ ] NEVER merges to upstream/automaker
**Dependencies**: M3-T2
**Blocks**: None
---
## 🚨 Orchestrator Review (Iteration 1)
**Status**: 🔴 Blocking - Starting iteration workspace
### Blocking Issues:
- 🔴 `apps/server/src/services/merge-gatekeeper.ts` - File not found
- 🔴 `apps/server/src/routes/github/routes/merge-request.ts` - File not found
### Required Actions:
1. CREATE `apps/server/src/services/merge-gatekeeper.ts` with:
- MergeGatekeeperService class
- checkMergeEligibility() method
- Poll PR status every 30s
- Validate PR is from `0xtsotsi/DevFlow`
- Create "ready for merge" task
- Auto-merge on human approval
2. CREATE `apps/server/src/routes/github/routes/merge-request.ts` with:
- API endpoint for merge requests
- Approval endpoint
- Merge execution endpoint
3. **CRITICAL**: Never merge to upstream/automaker
**Iteration**: 1/3
0xtsotsi
Contributor
merged
gsxdsm/vibe-kanban
3d
After a commit to the release branch, do a prod build (vibe-kanban)
Run the local build and update script with a git hook if possible. Don't rely on GitHub
gsxdsm
Contributor
merged
impactaky/shelffiles
3d
Move package.nix to example (vibe-kanban)
/openspec:proposal
Move package.nix to examples directory to avoid conflict with user change.
Instead, we should add instruction in README
impactaky
Contributor
merged
0xtsotsi/DevFlow
4d
M3-T3: Merge Gatekeeper with Human-in-the-Loop (vibe-kanban)
**Priority**: MEDIUM (enables safe auto-merge)
**Estimated**: 1 day
Create service that monitors PR status and notifies human for merge approval.
**⚠️ CRITICAL: FORK SAFETY**
- DevFlow is a fork of automaker
- origin = `0xtsotsi/DevFlow` ← **ALWAYS work here**
- upstream = `AutoMaker-Org/automaker` ← Read-only
- NEVER merge to automaker/upstream
**Files to Create:**
- `apps/server/src/services/merge-gatekeeper.ts`
- `apps/server/src/routes/github/routes/merge-request.ts`
**Implementation Details:**
```typescript
const DEVFLOW_REPO = "0xtsotsi/DevFlow";
interface MergeEligibility {
prNumber: number;
repository: string; // ⚠️ MUST validate = DEVFLOW_REPO
isEligible: boolean;
checks: {
ciPassed: boolean;
noComments: boolean;
noRequestedChanges: boolean;
approvals: number;
requiredApprovals: number;
};
}
interface MergeRequest {
prNumber: number;
repository: string;
requestedBy: string;
requestedAt: string;
status: 'pending' | 'approved' | 'rejected';
}
```
**Features:**
- Monitor PR status (CI checks, comments, approvals)
- **Repo validation**: Only process PRs from `0xtsotsi/DevFlow`
- When PR is "ready", notify human via:
- Desktop notification (Electron)
- Vibe Kanban task status change
- Human approves merge → auto-merge to DevFlow main
- Track merge metrics
**Acceptance Criteria:**
- [ ] Polls PR status every 30s when in "review" state
- [ ] Validates PR is from `0xtsotsi/DevFlow` repo
- [ ] Checks CI status, comment count, approval count
- [ ] Creates "ready for merge" task when all checks pass
- [ ] Auto-merges to DevFlow main on human approval
- [ ] Posts merge summary to PR
- [ ] NEVER merges to upstream/automaker
**Dependencies**: M3-T2
**Blocks**: None
---
## 🚨 Orchestrator Review (Iteration 1)
**Status**: 🔴 Blocking - Starting iteration workspace
### Blocking Issues:
- 🔴 `apps/server/src/services/merge-gatekeeper.ts` - File not found
- 🔴 `apps/server/src/routes/github/routes/merge-request.ts` - File not found
### Required Actions:
1. CREATE `apps/server/src/services/merge-gatekeeper.ts` with:
- MergeGatekeeperService class
- checkMergeEligibility() method
- Poll PR status every 30s
- Validate PR is from `0xtsotsi/DevFlow`
- Create "ready for merge" task
- Auto-merge on human approval
2. CREATE `apps/server/src/routes/github/routes/merge-request.ts` with:
- API endpoint for merge requests
- Approval endpoint
- Merge execution endpoint
3. **CRITICAL**: Never merge to upstream/automaker
**Iteration**: 1/3
0xtsotsi
Contributor
merged
Create tasks from other apps
Connect your favorite MCP client like Claude Desktop to access Vibe Kanban's capabilities directly from your personal AI assistant and extend your workflow beyond the interface.
This project is underrated. I've found it to be useful and fun.
Hamel Husain
Leading AI Consultant, 20 Years of Experience
Work from your IDE
Monitor agents, interact with them, perform code review, and see running processes directly in your IDE.
Motivation
Coding agents are reliable enough to be the default: We've built and tested coding agents for years and realised recently that reliability crossed an invisible threshold that means we now prefer starting most tasks with coding agents.
Coding agents are going to get much better: Coding agents have improved rapidly, and we expect this trend to continue. Imagine that in six months, 50% of the current failure modes of coding agents will get fixed, and six months after that another 50%. What will we (engineers) be spending our time on in that world? What tools would help us do that work most efficiently?
The SOTA will change: Foundational model labs and application layer startups will continuously leap-frog each other to build state-of-the-art coding agents over the next 12m+. You shouldn't have to change your workflow or behaviour to be able to try out different coding agents.
FAQs
Common questions about Vibe Kanban and how to get the most out of your AI coding agents
Yes, Vibe Kanban runs locally on your machine and doesn't send your code to external servers.
Vibe Kanban supports a wide range of coding agents including Claude Code, Gemini CLI, Cursor CLI, Amp, OpenAI Codex, Qwen Code, Opencode, and GitHub Copilot. You can find the complete list of supported agents in our documentation at vibekanban.com/docs. You can use multiple agents simultaneously and switch between them for different tasks.
Vibe Kanban itself is free and open source. You only pay for the underlying AI services (like Claude Code, OpenAI Codex, etc.) that you choose to use with your agents. There are no additional fees or subscriptions for using Vibe Kanban.
Absolutely! One of Vibe Kanban's key features is parallel execution. You can run multiple coding tasks simultaneously across different agents and projects. Each task runs in its own git worktree on your machine.
The VS Code extension brings the task view into your IDE. Search for 'Vibe Kanban' in the VS Code marketplace and it will automatically connect to your local Vibe Kanban instance.
MCP (Model Context Protocol) works with Vibe Kanban in two ways: First, you can connect MCP servers to your coding agents so they can access external resources and tools. Second, Vibe Kanban itself exposes an MCP server that you can connect to from third-party MCP clients like Claude Desktop, allowing you to seamlessly create tasks from third-party clients.
Yes! Vibe Kanban allows you to create reusable task templates to standardise your development processes. You can define templates for common tasks like bug fixes, feature implementations, or refactoring, which helps boost team productivity and consistency.
Yes, Vibe Kanban has seamless GitHub integration. It can automatically create pull requests after task completion, handle rebases and merges with one-click operations, and maintain clean git history. This makes it easy to incorporate AI-assisted development into your existing workflow.
Vibe Kanban provides real-time monitoring and control over agent execution. You can pause, resume, or stop agents at any time. The system also provides detailed logs and step-by-step visibility, making it easy to understand what went wrong and intervene when necessary.
Ready to get started?
Start managing your AI coding agents with Vibe Kanban.
Install Node.js 18+ then run:
$npx vibe-kanban