ogandreakiro

Codegen hosted in a way. Codegen is local and outputs a Playwright script. We add managed infra, observability, retries, and agent fallback recoveries when things break.

Similar goals but quite different execution and primitives

There are a few yes

Thanks :) We're Playwright / CDP under the hood

Yes. Record an automation flow, export the code, and share it. New users can run it as-is on our infra, or pick modify and run elsewhere.

Different from our core use case, but our agents can do open-ended exploration as well. You could prompt something like "navigate to this app as a new user and try common. flows" with structured outputs for findings. Session recording will show what happened. Not sure if it fully solves your problem - but happy to explore this together if you want to try it.

We're YC S25, launched in summer. Demonstrate Mode is a new feature we recently added to our platform and thought it would be worth sharing here.

Re differentiation: The space is crowded and feature sets converge. But like LLM providers, we feel there's room for multiple players with different positioning long term (enterprise, developers, etc.) Right now, we're now focused on making the product that feels most exciting to build with - hope people can tell that :)

Same spirit, yes. Record once, replay many. The difference now is when the page changes or an element moves, we have those fallback AI agents that can recover instead of just failing. But the core idea is the same; automate browser stuff.

Full circle indeed! We hope this iteration works better :)

Yes, that’s a very good point! We’ll look into this for SDK usage. What do you recommend for the public repo where it's harder to enforce runtime headers?

we’re working on fail-credit refunds so charges only apply to successful runs