Reflow

Reflow Studio turns a task in a web app into a how-to guide, and redoes the guide when the app changes. It is for support, onboarding and training teams who keep guides for software that keeps changing. In a 72-person survey we ran earlier, the top reason respondents gave for abandoning online learning was that the material didn't match their screen. For this hackathon, we added a Muse Spark layer to our existing Studio pipeline. Muse Spark 1.3 chooses actions from screenshots plus the labels and grid coordinates of the visible controls. Our new resolver maps each action to the real page element and a verified locator, so the run becomes guide steps that replay with no model choosing clicks. In a controlled test, we replaced the navigation templates of a local Gitea instance. The old guide's first step still matched an element and opened the wrong menu, and the next step failed. Without being given the new route, Spark found Workspace > Create new > New Repository. The repaired guide went from seven steps to eight and passed replay; the video, article, click-through demo and in-app walkthrough were regenerated, and the run stopped for human review. Separately, we benchmarked 11 everyday workflows on Gitea and Vikunja: all 11 were performed, replayed and filmed (two needed a retry, now automatic), and 10 of 11 completed in the existing Reflow player. New during the hackathon: the Spark computer-use executor, the pixel-to-element resolver, Meta's safety checks wired to our policy gate, SAM 3.1 drift evidence, Muse Voice Transcribe listen-back, Meta support for planning, compiling and judging, the Gitea redesign test, and a public mode with one-command setup. Existing before: Reflow's browser extension and player, which already has six paying customers in Korea, and the Studio prototype's DOM-agent pipeline, including its maintenance loop and basic policy gate.