Browser Use Ships workflow-use to Run Automations a Million Times Without AI

Browser Use launches workflow-use, an open-source tool that records browser actions once and replays them as deterministic, self-healing scripts — no LLM needed at run time.

·
·
Browser Use Ships workflow-use to Run Automations a Million Times Without AIPRO
  • workflow-use is a new open-source Python tool from the Browser Use team for recording browser workflows and replaying them deterministically.
  • You record browser actions once; an LLM converts them into a parameterized script; subsequent runs need no LLM at all.
  • A new Generation Mode lets you describe a task in plain English, runs Browser Use once to learn it, then stores a reusable workflow.
  • If a step breaks at runtime, the system falls back to the full Browser Use agent to self-heal — though this feature is still early.
  • The project is AGPL-3.0, free to use, requires an OpenAI API key only for generation/healing, and offers $10 free cloud browser credits.
  • The team explicitly warns it is not production-ready; the LLM fallback, step editor, and self-healing are all still rough or unfinished.

The team behind Browser Use , the Python library that lets LLMs control a browser via natural language , has shipped a companion open-source project called workflow-use. The pitch is simple: show the browser what to do once, and it will do it reliably, forever, without calling an LLM on every run.

Where Browser Use fell short

Browser Use was built for one-off tasks. Ask it to book a flight or look up a product and it works well. But enterprises kept asking for something different: a single workflow with dynamic variables , say, filling out a form with a new customer record , that runs a million times without breaking.

Enterprises typically have one workflow with dynamic variables that they want to reliably run a million times without breaking. Pure LLM agents were slow, expensive, and unpredictable for these high-frequency tasks. That gap is exactly what workflow-use is designed to close.

Record once, run forever

The core loop is straightforward:

  1. You manually record your browser interactions using a Chrome extension bundled with the repo.
  2. An LLM converts the recording into a deterministic, parameterized script stored as a .workflow.json file.
  3. You replay that script as many times as you want , with different input variables each time , and no LLM is invoked at runtime.

Pro article

This story is for Pro members

You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.

Comments

avatar