colanode

Open-source and local-first Slack and Notion alternative that puts you in control of your data

Runssource: GitHubhomepageTypeScriptApache-2.0commit d649523637f0

TypeScript, Apache-2.0 licensed. The project labels itself: chat, chat application, crdt, editor, electron, knowledge base, local first and notion.

colanode runs. An Argusic agent installed it in 3 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Repository installs and builds on Node 22, web app test suite passes 133 tests in 7 test files, server compiles to dist, desktop electron binary confirmed at v40.8.5.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
2
last tested
stars
5,146
forks
321
open issues
47
watchers
28
size
77 MB
created
last push

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.

Time lost to each failure while testing colanode, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node.js v18.19.1 incompatible with engine requirements (needs ^20.19.0 || ^22.12.0 || >=24.0.0)1 minute
  • Docker not available: server tests require Testcontainers for Postgres+Redis containers, and server runtime requires Postgres+Redis
  • Desktop app launch blocked: Electron sandbox not configured and dbus not available
Install time
3 minutes
Cold machine to finish
10 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
npm run build: 6 packages successful (0 failed); cd apps/web && npx vitest run: 7 test files passed, 133 tests passed
Model tokens used
48,685
Exact commit tested
d649523637f0
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.

**Install + Build:** both succeeded with Node 22. All 6 packages compiled, server dist generated, w…
**Tests:** Web test suite runs and passes — 7 files, 133 tests. Server tests need Docker (Testconta…
**Desktop:** Electron v40.8.5 binary confirmed via `--no-sandbox --version`. Full launch blocked by…
**Server:** Builds and compiles, but can't start without Postgres/Redis infrastructure.
tokens used
48,685
Now I have all the data needed. Here is my complete report:
**Error 1: Node.js version too old** — `npm install` failed on Node 18 because `@asamuzakjp/css-col…
**Install + Build:** both succeeded with Node 22. All 6 packages compiled, server dist generated, w…
**Tests:** Web test suite runs and passes — 7 files, 133 tests. Server tests need Docker (Testconta…
**Desktop:** Electron v40.8.5 binary confirmed via `--no-sandbox --version`. Full launch blocked by…
**Server:** Builds and compiles, but can't start without Postgres/Redis infrastructure.

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

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 3 minutes.
  • Recovered from all 3 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 Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 3 minutes after the clone.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.04
Argusic Runner1/3Runs100.000.19

Topics (from GitHub)

chatchat-applicationcrdteditorelectronknowledge-baselocal-firstnotionnotion-alternativerealtime-collaborationself-hostedslacksqliteteam-collaborationwikiyjs

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/colanode.svg)](https://argusic.com/subject/colanode)

Questions

Does colanode run?
Yes. colanode runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test colanode?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d649523637f0. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test colanode?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does colanode take to install?
3 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 colanode need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing colanode?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for colanode?
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.

Discussion