kanba
Kanba is an open-source project management tool for modern teams.
Runs with mockssource: GitHubhomepageTypeScriptMITcommit d5dfe822a503
TypeScript, MIT licensed. The project labels itself: kanban board, lists, notes, notion, project management, task management and trello.
kanba runs, with stand-ins for the services it depends on. An Argusic agent installed it in 55 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Kanba Next.js app installs, builds (npm run build exit 0), serves home/login/signup/dashboard pages, and completes real end-to-end flows (login, project creation, shared-board rendering) against a local schema-correct Supabase mock, with its API routes returning the correct validation statuses.
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.
- Mock .single() requests returned arrays, so project.id was undefined and the share page queried project_id=eq.undefined10 minutes
- Build failed: placeholder Supabase URL in .env.example is an invalid URL (ERR_INVALID_URL) during page-data collection for /api/stripe/webhook8 minutes
- Mock PostgREST filter parsing treated eq.X values as column names, so filters matched nothing6 minutes
- Mock returned empty arrays for embedded relations and dropped scalar columns on select=*,project_members!inner(role)6 minutes
- Mock returned 405 for HEAD requests used by the slug-uniqueness check5 minutes
- Mock lacked notifications table, listener views, and realtime WebSocket handshake, causing console errors5 minutes
- Install time
- 55 minutes
- Cold machine to finish
- 28 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- npm run build exited 0 (17 static pages); Playwright/Chromium against production server with local Supabase mock passed 8/8 flows: home 200, login->/dashboard, dashboard lists Welcome Board, project create POST 201 + redirect, project page shows name+columns, anon share board renders, /api/stripe/checkout 400 for missing params, /api/fetch-meta 500 without key
- Model tokens used
- 1,937,035
- Exact commit tested
- d5dfe822a503
- 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.
| Mock: `project_members!inner` returned empty / dropped scalar fields | Added embedded-relation an… | Mock: `.single()` requests returned arrays, breaking `project.id` | Return single object for `Acc… | Mock: `HEAD` requests returned 405 (slug-uniqueness check) | Added `HEAD` support to the PostgRES… | Browser CORS block on `accept-profile` header | Mock now returns `Access-Control-Allow-Headers: *… | Mock: login failed because Supabase client sends `grant_type` as query param | Mock reads `grant_… | Mock: missing `notifications`/view tables; realtime WS handshake error | Added tables/views and a… No error repeated 3×; all fixes landed. No system packages needed. ## Final state - `install_succeeded`: true — `npm ci` clean, `npm run build` exits 0. - `launch_succeeded`: true — production and dev servers start; app pages and flows respond. - `test_depth`: tier2_mock — verified behavior end-to-end through a locally stood-up schema-correct… - `verified_how`: `npm run build` exited 0 with 17 static pages; `curl` on `/`, `/login`, `/signup`…
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
- Installed in 55 minutes.
- Recovered from all 8 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
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.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 | 1/3 | Runs with mocks | 92.00 | 0.06 |
Topics (from GitHub)
kanban-boardlistsnotesnotionproject-managementtask-managementtrello
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/kanba)Questions
- Does kanba run?
- kanba runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 55 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test kanba?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d5dfe822a503. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test kanba?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does kanba take to install?
- 55 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 kanba need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing kanba?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for kanba?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.