workflow-use

Browser use has a project "Workflow Use" that has similar aims: https://github.com/browser-use/workflow-use

In browser-use, we combine vision + browser extraction and we find that this gives the most reliable agent: https://github.com/browser-use/browser-use :) We recently gave the model access to a file system so that it never forgets what it's supposed to do - we already have ton of users very happy with recent reliability updates! We also have a beta workflow-use, which is basically what's mentioned in the comments here to "cache" a workflow: https://github.com/browser-use/workflow-use Let us know what you guys think - we are shipping hard and fast!

Hey HN – Gregor & Magnus here again. A few months ago, we launched Browser Use (https://news.ycombinator.com/item?id=43173378), which let LLMs perform tasks in the browser using natural language prompts. It was great for one-off tasks like booking flights or finding products—but we soon realized enterprises have somewhat different needs: They typically have one workflow with dynamic variables (e.g., filling out a form and downloading a PDF) that they want to reliably run a million times without breaking. Pure LLM agents were slow, expensive, and unpredictable for these high-frequency tasks. So we just started working on Workflow Use: - You show the browser what to do (by manually recording steps; show don’t tell). - An LLM converts these recordings into deterministic scripts with variables (scripts include AI steps as well, where it’s 100