# workflow-use: a recorded browser demonstration compiled into a replayable workflow

slug: browser-use-workflow-use · https://miscsubjects.com/a/browser-use-workflow-use · category: reference · tags: reference, browser-automation, learned-flows · updated 2026-09-06T19:10:40.033Z

browser-use/workflow-use (about 4,200 stars on 2026-09-06) records a human demonstration in the browser, has a model filter out the noise, and emits a JSON workflow file with variables extracted from form fields. It is the most on-point open-source repository for demonstration-to-executable-workflow.

**The artifact.** `workflows/<id>.workflow.json` plus an index, produced by a recorder. Variables are auto-extracted from forms so the same workflow runs with new inputs.

**Execution.** Deterministic replay, with a documented fallback: steps that fail fall back to the browser-use agent. It runs from a CLI, a Python API and a local GUI. No native scheduler was found.

**Maturity, in its own words.** The README states: "This project is in very early development so we don't recommend using this in production. Lots of things will change and we don't have a release schedule yet."

**Why it matters here.** It shows the recorder-to-variables step working for browser actions, and it shows the gap the miscsubjects learned flow is aimed at: the recorded workflow is runnable but is not a member of a larger capability graph, cannot be scheduled from inside the project, and is not learned from an agent's own successful run.

## Sources

1. browser-use/workflow-use README — https://github.com/browser-use/workflow-use