The Vibe Kanban successor
Loved Vibe Kanban? Meet what comes next.
The kanban board for coding agents you already know — cards and lanes, an isolated workspace per task, Claude Code and Codex running in parallel — now with a Roadmap that grooms itself, dependencies that sequence the work, and a reviewed pull request at the end of every card.
A kanban board with four lanes — Ideating, Planning, Building and Shipping — carrying tasks from a fresh idea through to a pull request waiting for review.
Have a poke around
The Vibe Kanban flow: press Start, the card does the rest
Invented data, real mechanics. Press Start on a card and agents carry it across the lanes — refining, planning — until its plan comes back for your yes. Then it builds, tests and gets reviewed on its own.
Scroll a little further to load the demo
The board
Every piece of work, at the exact stage it's in. Positions aren't decoration — a card's column IS its state.
The inbox
One queue of everything blocked on you, each ask carrying the plan, the diff and the transcript behind it.
Activity
Who's working right now, on what, and what each run cost — live, with every finished run still on the record.
Engineer from anywhere
The same board, from your phone
Everything you liked about running agents from a kanban board, without being at the desk: press Start on the next card, and it plans, builds and opens a pull request while you're out.
From a beach chair
Scroll a little further to load the demo
Vibe Kanban alternative
Everything you loved about Vibe Kanban, carried forward
If Vibe Kanban changed how you work with coding agents, ampm keeps that shape and builds the rest of the engineering process around it.
- The board
- What you loved in Vibe Kanban:A kanban board for coding agents
- In ampm:The same board-first flow, with lanes for every step from planning to merged
- Parallel agents
- What you loved in Vibe Kanban:Many agents working at once
- In ampm:As many as your workers run, each card in its own isolated sandbox and checkout
- Your agents
- What you loved in Vibe Kanban:Claude Code, Codex and friends
- In ampm:Claude Code or Codex on the subscription you already pay for, with failover to a backup account
- Review
- What you loved in Vibe Kanban:Reading the diff before it lands
- In ampm:A test pass and a code-review seat on every card, then the PR waits for your merge — unless you want Autopilot to merge
- Planning the board
- What you loved in Vibe Kanban:Cards you created and ordered
- In ampm:Grooming merges duplicates, spreads priorities and links dependencies across the Roadmap — each change waits for your yes
- Task dependencies
- What you loved in Vibe Kanban:Cards that build on each other
- In ampm:A card waits for the one it needs to merge or deploy, then starts on its own
Dependency management
A web of dependencies? Fire and forget.
File tasks in any order. ampm works out what waits for what, and each card starts the moment the one it needs merges or deploys — no babysitting the board, no restarting agents by hand.
Have a poke around
Backlog grooming that sorts the board for you
Approve one grooming proposal: a duplicate folds away, priorities spread out, and the cards line up in the order they can be built — each one waiting on the card it needs.
Scroll a little further to load the demo
Have a poke around
Moving from Vibe Kanban takes minutes
Connect the repo you were using, add the repos agents should read for context, run one command to connect a worker on your machine or a server, and approve the onboarding pull request. Your board is ready.
- 1Start from
- 2Repos
- 3Read the repo
- 4Connect a worker
- 5Onboarding PR
- 6Your factory
Where does this factory start?
Kanban for coding agents
Built for people who think in cards
Drag to steer
Drag cards between Next, Soon and the Backlog. Agents pick up whatever is at the top, in dependency order.
Live cards
A pulsing dot means an agent is mid-turn on that card. Open it for the plan, the history and the full transcript.
Local or cloud workers
Paste one command on your laptop or a cloud server and it starts taking cards. Add workers to run more at once.
Self-hostable
Run the whole factory on your own infrastructure with Docker Compose. Workers run on the machines you choose.
Questions
Is ampm a Vibe Kanban alternative?
Yes. ampm is a kanban board for coding agents like Vibe Kanban was, running Claude Code or Codex on each card in its own isolated sandbox — and it adds backlog grooming, task dependencies, a test and code-review pass on every card, and an inbox for the decisions that are yours.
What happened to Vibe Kanban?
Bloop, the company behind Vibe Kanban, shut down in April 2026. The project continues as community-maintained open source. If you want a kanban for coding agents with a team behind it, ampm is built for the same way of working.
How do I move my Vibe Kanban board over?
Connect the same repo, connect a worker with one command, and paste your open tasks onto the Roadmap as ideas, as rough as they are. Grooming merges duplicates, sets priorities and links what depends on what.
Does ampm handle task dependencies?
Yes. A card can wait for another to merge or deploy. Grooming and breakdown link them for you, and a waiting card starts on its own the moment what it needs lands.
Is ampm affiliated with Vibe Kanban or Bloop?
No. ampm is an independent product. Vibe Kanban is named here only to describe who this page is for.
Which coding agents does ampm work with?
Claude Code and Codex. ampm runs them on the subscription you already pay for — no API keys and no second bill for tokens — and when one account hits its usage limit, work moves to a backup account without losing anything.
Does ampm merge code on its own?
Nothing merges unless you want it to. Plans, questions and merges wait in your inbox with the plan, diff, pull request and full transcript attached, and you decide which decisions to keep and which to hand off.
Where does the code run, and is my repo safe?
Every task runs in an isolated sandbox on its own worktree, on workers you choose — your laptop, a server you own, or a cloud machine — and can only push to a branch. The output is always a pull request into your repo.
How is this different from chatting with a coding agent?
A chat forgets everything when you close the tab and needs you watching it. ampm keeps every task in a database with its plan and history, runs a real process — plan, implement, test, review, merge — and only asks you when a decision is actually yours.
Can one workspace cover several repos?
Yes. Add the repos agents should change, and add more as read-only context — a design system, an API they call, product docs — so their work matches what's around it. One change can span several repos as one piece of work.
How do I get access?
Join the wait list with Google or GitHub. We're letting people in a few at a time, in the order they joined, and we'll email you when it's your turn.
Early access
Bring your board back to life
We're letting people in a few at a time. Join the wait list with Google or GitHub and we'll email you when it's your turn. Run it on our cloud or on infrastructure you control — your repos, your subscriptions, workers on machines you choose.