1. klntsky 29 minutes ago
    I told windsurf to install playwright, identify crucial workflows of the app and add tests for them. Not without my input, but I got what I wanted without getting the hands dirty.

    Does this thing add much on top?

  2. proc0 9 hours ago
    Interesting. I see from the video example it took a lot of steps and there is a lot of output for a simple task. I'm thinking this probably doesn't scale very well and more complex tasks might have performance challenges. I do think it's the right direction for AI coding.
    1. neversettles 9 hours ago
      Yeah, I suppose to esafak's point, perhaps a benchmark for browser agent QA testing would be needed.
  3. esafak 11 hours ago
    Is there a benchmark for this? If not, you ought to (crowd?)start one for everybody's sake.
  4. nico 11 hours ago
    Looks amazing. Congrats on the release

    How does this compare to browser mcp (https://browsermcp.io/)?

    1. neversettles 11 hours ago
      In browser MCP, looks like cursor controls each action along the way, but actually what we wanted was a single browser agent that had a high quality eval that could perform all the actions independently (browser-use)
  5. GreenGames 11 hours ago
    This is very cool! Does your MCP server preserve cookies/localStorage between steps, or would developers need to manually script auth handshakes?
    1. neversettles 11 hours ago
      Between steps it would preserve cookies, but atm when the playwright browser launches, it starts with a fresh browser state, so you'd have to o-auth to log in each time.

      We're adding browser state persistence soon, hoping to enable it so once you sign in with google once, it can stay signed in on your local machine.

      1. GreenGames 11 hours ago
        Oh okay thanks - that would be fire tbh