
Open-source framework to build AI web agents that automate browser tasks
By Tanmay Verma, Founder · Last verified 03 Jul 2026
In short
LaVague — Open-source framework to build AI web agents that automate browser tasks. Best for Developers building custom AI web agents for automation, QA engineers automating test writing with Gherkin specs, Teams needing adaptive browser automation that tolerates page changes. Free to use.
See what real users actually say. We scan live discussions, reviews and complaints across the web and hand you an honest verdict — in under a minute.
3 free scans · no card needed · downloadable report
LaVague is a solid open-source choice for developers who need custom web automation without writing brittle selectors. Its modular design and multiple driver support offer flexibility, but the setup and reliance on LLM API keys means it's not a zero-config solution. Worth trying for complex, dynamic workflows.
Compare with: LaVague vs Marvin, LaVague vs Zhipu GLM, LaVague vs MetaGPT
Last verified: July 2026
How likely is LaVague to still be operational in 12 months? Based on 4 signals — momentum (how recently it shipped), wrapper dependency, revenue model, and web presence.
Last calculated: July 2026
How we score →LaVague is an open-source framework designed for developers who want to create AI Web Agents to automate processes for their end users. The agents can take an objective, such as "Print installation steps for Hugging Face's Diffusers library," and generate and perform the actions required to achieve the objective. The framework consists of a World Model that interprets objectives and page context into step-by-step instructions, and an Action Engine that compiles those instructions into executable code like Selenium or Playwright commands. Targeted primarily at developers and QA engineers, LaVague lowers the barrier to creating reliable automation scripts. Instead of writing brittle selectors or page-specific logic, users define high-level goals, and the agent handles action generation and execution. The framework also includes LaVague QA, a specialized tool that converts Gherkin specifications into automated tests, making it a natural fit for testing workflows. Key features include built-in contexts for easy configuration, a test runner for benchmarking, a TokenCounter for estimating costs, logging tools, an optional Gradio interface, debugging tools, and a Chrome Extension. LaVague supports multiple drivers: Selenium, Playwright, and Chrome Extension drivers, with varying support for headless agents, iframes, and multiple tabs. The framework uses LLMs under the hood (default is GPT-4o, fully customizable), and costs depend on the models chosen, objective complexity, and website. Users can track token usage and estimate costs with the TokenCounter tool. Compared to alternatives like Playwright or Puppeteer scripts, LaVague offers a higher-level abstraction that adapts to page changes, though it requires hands-on setup and is best suited for developers comfortable with Python and automation concepts.
We see LaVague as a strong option for developers who want to build AI-powered web agents but don't want to reinvent the wheel. Its two-component architecture (World Model + Action Engine) is well thought out, and the ability to swap LLM backends gives it an edge over closed-source alternatives. The inclusion of LaVague QA for converting Gherkin specs into tests is a smart add-on for QA teams. When should you pick LaVague? If you're building a product that requires automated web navigation—like a web scraping service, a testing suite, or a workflow automation tool—and you want to avoid hardcoded selectors that break on page changes. It's also great for prototyping complex multi-step interactions without writing a line of Selenium code. When should you pass? If you need a plug-and-play solution for simple scraping tasks, you'd be better off with traditional scraping libraries or browser extensions. LaVague requires Python knowledge, API key setup, and an understanding of LLM cost implications. It's not for non-programmers. Compared to the closest alternative, Browserbase's Stagehand (another open-source web agent framework), LaVague offers more modularity with customizable drivers and deeper integration with LLM backends. However, Stagehand may have a simpler API for basic tasks. In practice, LaVague's debugging tools and test runner give it an edge for QA use cases. One real-world caveat: the default use of GPT-4o can rack up costs quickly if you run many steps. The TokenCounter helps, but you must actively monitor usage. Also, the Chrome Extension driver lacks headless and iframe support, which may limit some automation scenarios. Overall, LaVague is a promising framework for developers willing to invest in setup.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Common stack mates teams adopt alongside LaVague, with the specific reason each pairing earns its keep.
Used LaVague? Help shape our editorial sentiment research.