$ docwalk product
How it works
UI tutorials written by an agent, and replayed in CI so they never go stale. What docwalk does, what it’s built with, and how far along it is.
The premise
docwalk lets a coding agent write step-by-step tutorials for a desktop or web app on its own. It reads the code, drives the running app, takes screenshots with framewatch, marks them up, and saves the result as a portable tutorial package.
The same package replays as a test in CI. If a button moves or a label changes, the tour fails and tells you which step broke, so your docs get fixed at the same time as the UI. Native tours work on macOS and web tours work anywhere. Windows and Linux support is written but not yet verified.
What’s included
Records a tour by driving the real app, then replays it headless in CI with JUnit output
Four fallback ways to find each element, with weakened matches flagged in the pull request
Exports to Markdown, a standalone HTML viewer, Driver.js, Shepherd and MkDocs
An MCP server with a built-in skill, so any agent can write tours
How it’s built
docwalk is built on Rust, MCP, framewatch, Chrome DevTools Protocol and macOS Accessibility.
It carries 147 commits since Sep 2026, most recently changed in Sep 2026.
How the work is done
Every project here starts as a written spec, and the spec stays the source of truth once there’s code. The repository keeps a build plan with current status, an append-only decision log of where the code departed from the plan, and a handoff document that describes where things stand, including the unfinished parts.
That’s how one person keeps this many projects moving, and it’s what this page is written from.
Current state
Prototype. Works, but isn’t finished.
The source is private, so the way to check what this page says is to use the product.
Next
Put docwalk in your pipeline
Ask about hooking it up to the repositories and agents you already run.