How
None today. No MCP server, API or documented format; an agent could only drive scrimba.com through a browser like any user.
Interactive coding screencasts: pause the video, edit the teacher's code.
scrimba.com ↗docs ↗Format announcement (2017) ↗Launch HN (YC S20) ↗MDN partnership ↗Imba (the language Scrimba is built in, MIT) ↗
The best proof of the teaching model scene plans, but closed and web-only, so take the interaction design, not the product.
Borrow from it: take a specific idea, API or format.
Scrimba proved, years before anyone said 'agent tours', that the right primitive for teaching software is a recording of events rather than pixels. Because the screencast is a replay of real editor state, the learner can stop at any second and be inside the instructor's actual code, editing and running it, then resume the narration. That one move removes the biggest failure of video tutorials (copying code line by line, setup breakage) and it scaled: a paying multi-path coding school with over a million learners and MDN's endorsement. Its authoring story is also humane: press record and talk while you code; no editing suite. If you want to know whether 'narrate, then let the learner take over' works pedagogically and commercially, Scrimba is the existence proof.
| UI as data | 2 scene 5 | The recording is an event log internally, but proprietary and not exposed as a value anyone can store or diff. |
|---|---|---|
| Agent can drive it | 0 scene 5 | |
| Agent can see it | 0 scene 5 | |
| Small, targeted edits | 0 scene 5 | |
| Time travel | 3 scene 0 | Learner can scrub, pause and fork-by-editing; human-facing only. |
| Live data rate | 0 scene 5 | |
| Terminal native | 0 scene 5 | |
| Pixel graphics | 4 scene 4 | |
| Teaching | 5 scene 3 | Built around exactly record, narrate, take over, rewind. |
| Maturity | 4 scene 1 | Years in production, large learner base, MDN partner. |
| Openness | 0 scene 4 | Fully proprietary. |
Scrimba scene now scene planned
None today. No MCP server, API or documented format; an agent could only drive scrimba.com through a browser like any user.
Not feasible beyond browser automation; recording/authoring is a human-in-browser flow.
Only via screenshots/DOM scraping of the web app.
No addressable edits for an agent; a human edits code in the paused scrim.
Human scrubbing and rewind of the recording; nothing exposed to an agent.
The best model of 'teacher narrates, learner takes over', but a sealed product with no agent surface.
A scrim is a recording of editor and browser events plus the instructor's audio, not a pixel video. Playback re-creates the instructor's actions in a live in-browser IDE in the same environment, so at any moment the learner can pause, edit, run and copy the code. The IDE and the player are one tool, built in Imba. Execution is client-side (browser), which is why backend topics were hard to support early on.
No published numbers. The 2017 post argues file-size and searchability advantages qualitatively.
CEO's LinkedIn describes a 1.5M+ learner platform; the 2020 Launch HN reported 3,000 paid enrolments in the first career path. MDN chose Scrimba as its recommended course partner in 2024.
Used by: MDN Web Docs (recommended course partner for the MDN Curriculum)
A going commercial concern with steady content output, but nothing an outsider can maintain or fork.
Releases: Continuous SaaS deploys; no public versioning. A v2 platform replaced v1 (v1.scrimba.com still reachable for legacy recording). · Recent: Active: 2026 articles, AI Engineer path, AI tutor built into Pro (per scrimba.com articles). · Bus factor: medium: small private company; the platform rests on a niche in-house language (Imba) whose author is the CTO.
The teaching-tour concept: a narrated, replayable sequence where the learner can take over mid-stream and rewind.
The record-events-not-pixels format and the pause-and-take-over interaction; Scrimba already shipped and validated both, for code in a browser.
An agent as the live narrator in a terminal, with a documented, open state/event format the agent can read, seek, fork and replay; Scrimba has no agent surface, no terminal and no open format.
| 1–7 | home · features · use cases · docs · changelog · under the hood · blog |
| t | light or dark |
| j k | scroll |
| g G | top · bottom |
| ? Esc | this · close |