markeron
Lightweight (~1.5 MB) open-source screen annotation with click-through mode and keyboard-first shortcuts. For demos, teaching, meetings & screen recording. Windows, macOS.
Could not verifysource: GitHubhomepageTypeScriptMITcommit 3e87b1cc2980
TypeScript, MIT licensed. The project labels itself: canvas, desktop annotation, desktop app, drawing, macos, productivity, rust and screen annotation.
Argusic could not get markeron running. An Argusic agent installed it in 24 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.
All frontend infrastructure works: Node 24.15.0, npm 11.12.1, dependencies installed, 346/346 vitest tests pass, TypeScript typechecks clean, Vite build succeeds, lint and format 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 36.7 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.
- Missing GTK3/GLib/WebKit system dev libraries for Tauri Rust build20 minutes
- Node.js v18.19.1 in container instead of required v24.15.02 minutes
- Rust/Tauri cargo check fails on Linux by design - compile_error! guard at src/lib.rs:2
- Install time
- 24 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 3 hit, 2 fixed with no human help
- How the result was proved
- npm test: 346 vitest tests passed (29 files) + 4 node scripts passed, exit 0. npm run build:fe: vue-tsc --noEmit + vite build produced dist/, exit 0. npm run lint: 0 errors, exit 0. npm run format:check: all files use Prettier style, exit 0.
- Model tokens used
- 225,478
- Exact commit tested
- 3e87b1cc2980
- 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.
**Frontend verification:** 346 vitest tests pass across 29 test files, 4 additional `node --test` s…
**Rust/Tauri backend:** The project contains `compile_error!("MarkerOn only supports Windows and ma…
**App launch:** Not applicable — this is a Tauri v2 system-tray application that requires the compi…
tokens used
225,478
Now I have all the data for the final report.
Here is the complete assessment:
**Node setup:** installed via nvm, matches the project's `.nvmrc` pin (v24.15.0, npm 11.12.1)
**npm install:** succeeded (281 packages, 282 audited)
**Frontend verification:** 346 vitest tests pass across 29 test files, 4 additional `node --test` s…
**Rust/Tauri backend:** The project contains `compile_error!("MarkerOn only supports Windows and ma…
**App launch:** Not applicable — this is a Tauri v2 system-tray application that requires the compi…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
- 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
- An agent with no time limit did not get it running.
- Took 24 minutes to install, slower than the median of the 8 comparable projects Argusic has measured.
- Hit 3 errors during setup, 1 of which were not solved.
Of the 9 canvas projects Argusic has installed and timed, markeron was the 8th fastest to reach a running state, and 6 of 9 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 | Did not run | 43.33 | 0.14 | |
| Argusic Runner | 1/3 | Did not run | 30.00 | 0.04 |
Topics (from GitHub)
canvasdesktop-annotationdesktop-appdrawingmacosproductivityrustscreen-annotationtailwindcsstauritauri-apptypescriptvitevuevue3vue3-typescriptwhiteboardwindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/markeron)Questions
- Does markeron run?
- Argusic could not verify that markeron runs. Argusic installed and launched it on a clean machine in 24 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test markeron?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3e87b1cc2980. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test markeron?
- The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does markeron take to install?
- 24 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 markeron need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing markeron?
- 3 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does markeron compare with the alternatives?
- Of the 9 canvas projects Argusic has installed and timed, markeron was the 8th fastest to reach a running state, and 6 of 9 reached one at all.
- Where is the evidence for markeron?
- 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.