Show HN: Stagehand – an open source browser automation framework powered by AI
61–70 of 89 posts
Re: Show HN: Stagehand – an open source browser automation framework powered by AI
#62Does this open up the possibility of automating an existing open browser tab? (Instead of a headless or specifically opened instance of chrome?)
Re: Show HN: Stagehand – an open source browser automation framework powered by AI
#63I've been playing around with Stagehand for a minute now, actually a useful abstraction here. We build scrapers for websites that are pretty adversarial, so having built in proxies and captcha is delightful. Do you guys ever think you'll do a similar abstraction for MCP and computer use more broadly?
Thanks so much! Our Stagehand MCP server actually won Anthropic's Claude MCP hackathon :) Check it out: https://github.com/browserbase/mcp-server-browserbase/tree/m... We're working on a better computer use integration using Stagehand, def a lot of interesting potential there
Re: Show HN: Stagehand – an open source browser automation framework powered by AI
#64Any attempt on doing something similar but as a browser extension?
Re: Show HN: Stagehand – an open source browser automation framework powered by AI
#65wow. It's like cursor vs vscode movement but for browser automation and scrapping. Kudos to the author. Are there any other similar tools?
Re: Show HN: Stagehand – an open source browser automation framework powered by AI
#66Earlier quoted context omitted.
Yes, you can certainly use Ollama! However, we strongly recommend using a more beefed up model to get sustainable results. Check out our external_client.ts file in examples/ that shows you how to setup a custom LLMClient: https://github.com/browserbase/stagehand/blob/main/examples/... >
It doesn’t look like accessing the llmclient for this is possible for external projects in the latest release, as that example takes advantage of being inside the project. (At least working through the quick start guide).
Re: Show HN: Stagehand – an open source browser automation framework powered by AI
#67Cool to see another open source AI browser testing project! There’s a couple of others I’ve heard of as well: Skyvern: https://github.com/Skyvern-AI/skyvern Shortest: https://github.com/anti-work/shortest I’d love to hear what makes Stagehand different and pros/ cons. Of course, I have no complaints to see more competition and open source work in this space. Keep up the great work!
However with Stagehand, because it's an extension of Playwright, it allows you to confirm each step of the underlying agent's workflow, making it the most customizable option for engineers who want/need that
Re: Show HN: Stagehand – an open source browser automation framework powered by AI
#68Does this open up the possibility of automating an existing open browser tab? (Instead of a headless or specifically opened instance of chrome?)
Afaik no. But if it's access to authenticated resources that you want, you can do so by copying over cookies.
npx create-browser-app --example persist-contextRe: Show HN: Stagehand – an open source browser automation framework powered by AI
#69Cool! Before building a full test platform for testdriver.ai we made a similar sdk called Goodlooks. It didn't get much traction, but will leave it here for those interested: https://github.com/testdriverai/goodlooks
Re: Show HN: Stagehand – an open source browser automation framework powered by AI
#70Earlier quoted context omitted.
It's funny you mentioned "deterministic Playwright code," because in my experience, that’s one of the most frustrating challenges of writing integration tests with browser automation tools. Authoring tests is relatively easy, but creating reliable, deterministic tests is much harder. Most of my test failures come down to timing issues—CPU load subtly affects execution, leading to random timeouts. This makes it diffic…
I was working on a side project over the holidays with the (I think) same idea as mpalmer imagined there too (though my project wouldn't be interested to him either, because my goal wasn't automating tests) Basically, the goal would be to do it like with screenshot regression tests: basically you get 2 different execution phases: - generate - verify And when verify fails in CI, you can automatically run a generate an…