kaneo
🎯 All you need. Nothing you don't. Open source project management that works for you, not against you.
Runssource: GitHubhomepageTypeScriptMITcommit 6e47ef666d5f
TypeScript, MIT licensed. The project labels itself: hono, issue management, issue tracker, jira alternative, kanban, linear alternative, mcp and project management.
kaneo runs. An Argusic agent installed it in 26 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Node 24.21.0 with pnpm 10.32.1, PostgreSQL 16.1 compiled and running, all dependencies installed, database migrated, API builds and serves /api/config at localhost:1337, web app builds in 13.9s, 506 API unit tests, 332 web unit tests, and 79 integration tests pass.
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 100 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.
- PostgreSQL not installed and no root apt/docker8 minutes
- Node.js v18.19.1 too old (requires >=24)2 minutes
- pnpm not found1 minute
- npm global install failed due to /usr/local permissions1 minute
- DATABASE_URL derivation requires POSTGRES_PASSWORD when POSTGRES_* vars are set1 minute
- Integration tests require kaneo_test database1 minute
- Install time
- 26 minutes
- Cold machine to finish
- 27 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- curl -s http://localhost:1337/api/config returned 200 with full JSON config object; pnpm test:unit passed 506/506; apps/web pnpm test passed 332/332; integration tests passed 47/47 (workspace-rbac, label-crud, workspace-settings) and 79/79 (5 files combined); packages permissions (10/10), email (24/24), libs (3/3) all passed
- Model tokens used
- 545,068
- Exact commit tested
- 6e47ef666d5f
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
| Permissions | 1 | 10 | ✅ all passed |
| Email | 7 | 24 | ✅ all passed |
| Libs | 1 | 3 | ✅ all passed |
| Integration (5 files) | 5 | 79 | ✅ passed |
| **Total verified** | **164** | **954** | **all ✅** |
**Live API verified:** `curl http://localhost:1337/api/config` returned `{"disableRegistration":fal…
**Integration tests note:** Running the full integration suite (all ~30+ files) takes longer than a…
exec
/bin/sh -lc 'pkill -f "node dist/index" 2>/dev/null; pg_ctl -D /home/runner/pg/data stop 2>/dev/nul…
exited 143 in 0ms:
tokens used
545,068Replay 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
- Reached a running state on a clean machine, with the session recorded.
- Installed in 26 minutes.
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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
Topics (from GitHub)
honoissue-managementissue-trackerjira-alternativekanbanlinear-alternativemcpproject-managementreactself-hostedtypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/kaneo)Questions
- Does kaneo run?
- Yes. kaneo runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test kaneo?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6e47ef666d5f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test kaneo?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does kaneo take to install?
- 26 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 kaneo need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing kaneo?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for kaneo?
- 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.