notion-electron
Notion Desktop Client for Linux
Runssource: GitHubTypeScriptMITcommit 92918ebab0fc
TypeScript, MIT licensed. The project labels itself: electron, javascript, nodejs, notion, office and productivity.
notion-electron runs. An Argusic agent installed it in 7 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The repository installs (npm install), builds (npm run build emits complete main/preload/renderer output), typechecks (tsc --noEmit passes all three tsconfigs), lints (ESLint + Prettier pass), and the Electron application launches and runs persistently on a virtual X display (state S, killed by timeout after 20s) with only expected container-related D-Bus warnings.
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 90 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.
- themeService.queryColorScheme() calls freedesktop portal D-Bus API unavailable in container, crashing app3 minutes
- Node.js v18 in container, project requires v22+2 minutes
- chrome-sandbox SUID helper needs root ownership (container limitation)1 minute
- Install time
- 7 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- timeout 20 ./node_modules/electron/dist/electron --no-sandbox --disable-gpu out/main/index.js with DBUS_SESSION_BUS_ADDRESS set to a running session bus daemon, process stayed running for full duration, state S (sleeping/normal), killed by timeout, no crashes. Also passed typecheck (0 errors) and lint:all (0 errors).
- Model tokens used
- 204,023
- Exact commit tested
- 92918ebab0fc
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
|---|---| | `npm install` | 570 packages, 0 errors | | `npm run build` | main + preload + renderer all built | | `npm run typecheck` | 0 errors across 3 tsconfigs | | `npm run lint:all` | 0 errors | | Direct app launch | Process ran for 20s (killed by timeout), state S | | `npm run preview` | Blocked by chrome-sandbox SUID (needs root) | **Fixes applied:** 1. **Node v18→v22**: Installed nvm + Node 22.23.4 2. **D-Bus portal crash**: Caught the rejected promise from `queryColorScheme()` so the app starts … 3. **Sandbox helper**: Used `--no-sandbox` flag (container limitation) The only remaining container-specific gap is the system D-Bus socket (`/run/dbus/system_bus_socket`…
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.
- 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 MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 7 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
Of the 6 electron projects Argusic has installed and timed, notion-electron was the 4th fastest to reach a running state, and 4 of 6 reached one at all.
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 7 minutes after the clone.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.04 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.05 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/notion-electron)Questions
- Does notion-electron run?
- Yes. notion-electron runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test notion-electron?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 92918ebab0fc. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test notion-electron?
- 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 notion-electron take to install?
- 7 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 notion-electron need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing notion-electron?
- 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.
- How does notion-electron compare with the alternatives?
- Of the 6 electron projects Argusic has installed and timed, notion-electron was the 4th fastest to reach a running state, and 4 of 6 reached one at all.
- Where is the evidence for notion-electron?
- 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.