explainroo
Explainer videos and product demos made by your AI agent. Free and open source: a local voice (Kokoro), word timing (Whisper) and a canvas renderer turn a script into a narrated MP4.
Runssource: GitHubhomepageJavaScriptMITcommit 9ad2881d02ea
JavaScript, MIT licensed. The project labels itself: ai agents, animation, canvas, claude code, codex, explainer video, ffmpeg and javascript.
explainroo runs. An Argusic agent installed it in 7 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
explainroo installs, all 38 tests pass, doctor checks green on node/ffmpeg/chrome/voice/speech models, and a 3-scene 19-second test video was written, rendered, verified with 100% speech clarity and no ffmpeg errors.
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.
- Chrome/Chromium not found12 minutes
- speech/voice models not downloaded9 minutes
- Node.js v18.19.1 below required >=20.112 minutes
- sharp binary built for Node 18 rejects Node 201 minute
- Install time
- 7 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- node --test test/*.test.js exited 0 with 38/38 passed; node bin/explainroo.js doctor exited 0 confirming node/ffmpeg/chrome/voice/speech; node bin/explainroo.js voice videos/test-video produced 19.3s narration at 100% confirmation; node bin/explainroo.js check videos/test-video reported 'no problems found'; node bin/explainroo.js still videos/test-video produced 3 PNG stills via Chrome headless; node bin/explainroo.js render videos/test-video --draft produced draft.mp4; ffmpeg -v error -i out/draft.mp4 -f null - returned no decoding errors; node bin/explainroo.js verify videos/test-video reported loudness -14.1 LUFS, true peak -1.5 dBFS, narration understood 100%
- Model tokens used
- 69,695
- Exact commit tested
- 9ad2881d02ea
- 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.
- **check**: "no problems found in 3 scenes (19.3s)" - **still**: captured 3 still frames via Chrome headless for each scene end - **render --draft**: wrote `out/draft.mp4` (960x540, 579 frames, 9.2s) with no ffmpeg errors - **verify**: "narration understood: 100%", loudness -14.1 LUFS, true peak -1.5 dBFS ## Errors 1. **Node v18.19.1 too old**: project requires >=20.11. Fixed by downloading and using Node v20.18.… 2. **Chrome not found**: fixed by running `npx playwright install chromium-headless-shell`. 3. **Sharp binary mismatch**: built for Node 18 but project needs Node 20+. Fixed by reinstalling `… 4. **Speech models not downloaded**: fixed by running `doctor --fetch`. 5. **pthread_setaffinity_np errors** from onnxruntime (stderr): These are benign container affinity… ``` ```
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 4 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 123 comparable projects Argusic has measured.
Of the 124 ai-agents projects Argusic has installed and timed, explainroo was the 72nd fastest to reach a running state, and 96 of 124 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.
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)
ai-agentsanimationcanvasclaude-codecodexexplainer-videoffmpegjavascriptkokoroproduct-demotext-to-speechvideo-generationwhisper
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/explainroo)Questions
- Does explainroo run?
- Yes. explainroo runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test explainroo?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9ad2881d02ea. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test explainroo?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does explainroo 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 explainroo need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing explainroo?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does explainroo compare with the alternatives?
- Of the 124 ai-agents projects Argusic has installed and timed, explainroo was the 72nd fastest to reach a running state, and 96 of 124 reached one at all.
- Where is the evidence for explainroo?
- 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.