Repository navigation
Status and Roadmap
Archi edited this page Oct 18, 2026
·
2 revisions
What DemoFlow can do today, what ships in the next npm release, and what is planned but not built. The source of truth is the roadmap and the spec index; this page summarises them.
| Area | Status |
|---|---|
| Scenario format, validation, JSON Schema | built |
demoflow run, validate, setup
|
built, in 0.1.0
|
demoflow mcp (Claude Code) |
built, in 0.1.0
|
| Secrets from env and masked fields | built, in 0.1.0
|
| Cursor, click rings, zoom, captions, idle compression, failure card | built, in 0.1.0
|
press step and key badge |
built on develop — next release |
devCommand: run starts the app |
built on develop — next release |
demoflow record |
built on develop — next release |
| Rounded window frame and background | built on develop — next release |
| Intro, scene and outro cards | not built — in progress (#108) |
| Fade transitions | not built |
| GIF, WebM and 9:16 export | not built |
| Website, accounts, projects, library | not built (scaffolding only) |
| Runner pairing | not built |
| Luna Player playback | not built |
| SDK and GitHub Action | not built |
The roadmap runs in phases; each phase is split into small issues with one spec each.
-
Phases 1–3 — done. Core contracts, engine, renderer, CLI and the MCP server; the first npm release
demoflow@0.1.0. -
Between 3 and 4 — done on
develop.demoflow record, thepressstep, visual baselines for rendered output. - Phase 4 — Video quality (in progress). Screen Studio-like look: frame and background (done), then cards and transitions, then export formats.
- Phase 5 — Website and Runner pairing. Personal accounts, sign-in, pairing a local Runner, projects and the demo library; production at the end of the phase.
- Phase 6 — Playback through Luna Player behind an adapter.
- Phase 7 — SDK and integrations: mask attributes, a ready signal, annotations, Playwright tests as scenarios; a GitHub Action in a separate repository.
flowchart LR
P13["Phases 1–3<br/>run · MCP · npm 0.1.0"]:::done --> PR["record · press<br/>visual baselines"]:::done
PR --> P4["Phase 4<br/>video quality"]:::wip
P4 --> P5["Phase 5<br/>website · Runner"]:::todo
P5 --> P6["Phase 6<br/>playback"]:::todo
P6 --> P7["Phase 7<br/>SDK · integrations"]:::todo
classDef done fill:#d3f9d8,stroke:#2b8a3e,color:#000
classDef wip fill:#fff3bf,stroke:#e67700,color:#000
classDef todo fill:#f1f3f5,stroke:#868e96,color:#000
- Track work in open issues; each feature issue links its spec under
docs/specs/. - Check what an npm version contains with
npx demoflow --help— commands missing there are not in that release.
- A planned item has no date. The product vision describes more than the roadmap commits to (for example
demoflow loginanddemoflow runner …); none of those commands exist. - The website will have no public share links and no pricing in Phase 5 (roadmap).
- Home · Architecture · FAQ
- Roadmap · Spec index · ADR index
- Planned design: ADR-0006 — accounts, ADR-0007 — Runner pairing, ADR-0009 — playback
DemoFlow · Issues · Decision records · Specs · MIT licensed
Start
Features
- Scenarios
- Recording Scenarios
- Running Demos
- Rendering and Effects
- Secrets and Masking
- Run Artifacts
- MCP Server
Operate
Reference