Vibe Kanban Alternative: Foxpit for Claude Code, Codex and OpenCode

Vibe Kanban is sunsetting: its README opens with "Vibe Kanban is sunsetting." and the project site adds that "The project will continue as open source and community maintained." If you are deciding where your agent workflow lives next, this page compares the two honestly and gives a short path to move.

Vibe Kanban in short

Vibe Kanban is a board for planning agent work and then running it. Its own description is to "Get 10X more out of Claude Code, Codex or any coding agent" by planning with kanban issues and creating workspaces where agents execute them (github.com/BloopAI/vibe-kanban).

• Interface: a local web app started with npx vibe-kanban, plus packaged desktop builds (.msi, .exe and .deb assets on the release page).
• Operating systems: Windows, macOS and Linux. The release assets and notes cover all three.
• Agents: Claude Code, Codex, Gemini CLI, GitHub Copilot, Amp, Cursor, OpenCode, Droid, CCR and Qwen Code.
• Git worktrees: yes. The site lists "Automate creating git worktrees and running setup scripts", and DISABLE_WORKTREE_CLEANUP turns cleanup off.
• Price and licence: Apache-2.0 open source. No paid plan price is stated on the pages we checked.
• Latest release: v0.1.44, 24 April 2026 (releases).

The status needs its own sentence, in the project's words. The repository README begins with "Vibe Kanban is sunsetting." The v0.1.42 release note says "bloop, the company behind Vibe Kanban is shutting down". The site adds: "The project will continue as open source and community maintained." Those three sentences come from the repository, the releases page and vibekanban.com. The code is still there to read; what changed is the direction, because fixes and features now depend on whoever picks the project up.

Foxpit vs Vibe Kanban at a glance

When Vibe Kanban is the better choice

A comparison that only lists the new tool's wins is not worth reading. These are the cases where Vibe Kanban is the right answer:

• You want a board first. Planning with issues on a kanban board is the centre of the product, not an add-on. If your team already thinks in tickets, it fits without translation.
• The agent you need is not in Foxpit. Gemini CLI, GitHub Copilot, Amp, Cursor, Droid and Qwen Code are supported there and not in Foxpit today. That alone can decide it.
• You want to run it yourself. Apache-2.0 means you can read the code, fork it and keep your own build. A community-maintained project can outlive the company, and you are allowed to help.
• You prefer the browser. One command starts it and the UI is a local web page. No desktop install, no separate app window.

If it already works for you, there is no emergency: the sunset notice changes the roadmap, not your repository.

When Foxpit fits better

Foxpit is a desktop app for running Claude Code, Codex, OpenCode and Antigravity as one team in rooms, one room per project.

• Memory survives the agent switch. Every agent in a project reads the same memory, so a Codex session already knows what the Claude Code session decided yesterday. That matters most when a board hands one issue to one vendor and the next issue to another.
• One lead does the splitting. Fox turns a goal into task cards with checklists, assigns them to teammates and reports back, instead of you writing the same plan into each workspace.
• Approvals and limits do not need babysitting. Permission requests arrive as desktop notifications, and when Claude Code hits its 5-hour limit Fox parks the turn and sends "continue" at the reset.

Moving from Vibe Kanban to Foxpit

1. Download and start the trial. Grab the build for your system from Getting Started. The trial runs for 3 days with every feature and needs no card.
2. Keep your agent CLIs as they are. Foxpit drives the tools you already installed and logged in. Nothing about Claude Code, Codex or OpenCode has to be reconfigured.
3. Add the project as a room. Point it at the repository you were running on the board. Recreate your open issues as task cards; closed ones can stay closed.
4. Turn on worktrees before the first parallel run. One worktree per agent keeps two teammates from editing the same files while they work on different cards.

Frequently asked questions

Related: Alternatives and comparison and What an AI coding agent orchestrator does.