⚙️ Workflow Use is the easiest way to create and execute deterministic workflows with variables which fallback to Browser Use if a step fails. You just show the recorder the workflow, we automatically generate the workflow.
❗ 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. Originally, the project was born out of customer demand to make Browser Use more reliable and deterministic.
git clone https://github.com/browser-use/workflow-use
cd extension
npm install
npm run build
cd workflows
uv sync
playwright install chromium
cp .env.example .env
workflow-use-demo.mp4
workflow-use-gregor-demo.mp4
- 🔁 Record Once, Reuse Forever: Record browser interactions once and replay them indefinitely.
- ⏳ Show, don't prompt: No need to spend hours prompting Browser Use to do the same thing over and over again.
- ⚙️ Structured & Executable Workflows: Converts recordings into deterministic, fast, and reliable workflows which automatically extract variables from forms.
- 🪄 Human-like Interaction Understanding: Intelligently filters noise from recordings to create meaningful workflows.
- 🔒 Enterprise-Ready Foundation: Built for future scalability with features like self-healing and workflow diffs.
Show computer what it needs to do once, and it will do it over and over again without any human intervention.
- Nice way to use the .json files inside python code
- Improve LLM fallback when step fails (currently really bad)
- Self healing, if it fails automatically agent kicks in and updates the workflow file
- Better support for LLM steps
- Take output from previous steps and use it as input for next steps
- Expose workflows as MCP tools
- Use Browser Use to automatically create workflows from websites
- Improve CLI
- Improve extension
- Step editor
- Allow Browser Use to use the workflows as MCP tools
- Use workflows as website caching layer
English (US) ·