vibe-kanban
Get 10X more out of Claude Code, Codex or any coding agent
Runs with mockssource: GitHubhomepageRustApache-2.0commit d5cbb5380fa0
Rust, Apache-2.0 licensed. The project labels itself: agent, ai agents, kanban, management and task manager.
vibe-kanban runs, with stand-ins for the services it depends on. An Argusic agent installed it in 48 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Rust workspace (excluding tauri-app) compiles and passes cargo check. Server binary builds and starts, binding to random available port and responding to HTTP requests. 3 crate test suites pass (10/10 unit tests). Frontend TypeScript type checks pass for web-core and local-web. The npx CLI, Tauri desktop app, and web dev server were not verified due to disk constraints and missing GTK system libraries.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- libsqlite3-sys build failed: requires libclang for bindgen (no clang-dev installed)20 minutes
- LLVM 18.1.8 downloaded first but needed libtinfo.so.5 (NCURSES_TINFO_5.0.19991023 version mismatch)15 minutes
- Disk space exhaustion (40GB overlay): cargo test/test binaries and LLVM filled disk5 minutes
- Rust toolchain not found (no rustup, cargo, or rustc)3 minutes
- pnpm not installed, npm install -g failed due to EACCES on /usr/local/lib1 minute
- .npmrc had engine-strict=true blocking install on Node 18 (requires >=20)1 minute
- Install time
- 48 minutes
- Cold machine to finish
- 82 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- cargo test -p db --lib (3/3 passed), cargo test -p git --lib (2/2 passed), cargo test -p utils --lib (5/5 passed), pnpm run web-core:check (tsc --noEmit passed), pnpm run local-web:legacy-path-guard (all checks passed), target/debug/server started and responded to HTTP on dynamic port
- Model tokens used
- 1,285,206
- Exact commit tested
- d5cbb5380fa0
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
2026-09-25T19:05:38.685848Z WARN executors::executors::opencode: Failed to spawn OpenCode server: … Server output tail: 2026-09-25T19:05:39.183371Z WARN executors::executors::opencode: Failed to spawn OpenCode server: … Server output tail: 2026-09-25T19:05:39.447955Z INFO server: Shutdown signal received 2026-09-25T19:05:39.448096Z INFO local_deployment::container: Killing all running processes 2026-09-25T19:05:39.450720Z INFO local_deployment::container: Found 0 running processes to kill Now let me compile the final comprehensive result. 2026-09-25T19:06:05.475181Z ERROR codex_core::session: failed to record rollout items: thread 01a0d… tokens used 1,285,206 Now let me compile the final comprehensive result.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 48 minutes to install, slower than the median of the 137 comparable projects Argusic has measured.
Of the 138 agent projects Argusic has installed and timed, vibe-kanban was the 136th fastest to reach a running state, and 92 of 138 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.31 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.14 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vibe-kanban)Questions
- Does vibe-kanban run?
- vibe-kanban runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 48 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test vibe-kanban?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d5cbb5380fa0. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test vibe-kanban?
- The run that produced this verdict cost $0.31: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does vibe-kanban take to install?
- 48 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does vibe-kanban need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing vibe-kanban?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does vibe-kanban compare with the alternatives?
- Of the 138 agent projects Argusic has installed and timed, vibe-kanban was the 136th fastest to reach a running state, and 92 of 138 reached one at all.
- Where is the evidence for vibe-kanban?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.