Show HN: Libretto – Making AI browser automations deterministic

Super cool! Please let me know how it goes. Since agents are so good at writing code, we think letting the agent rewrite/test the code on failure is better than just using a prompt at runtime

I literally _just_ put up an announcement on our internal Slack of a tool I had spent a few weeks trying to get right. Strange to post the announcement and, literally the same day, see a better, publicly available toolkit to do enable that very workflow!

I'm also using Playwright, to automate a platform that has a maze of iframes, referer links, etc. Hopefully I can replace the internals with a script I get from this project.

[dead]

There are a couple ways to handle JS components rendered at runtime:

- Libretto prefers network requests over DOM interaction when possible, so this will circumvent a lot of complex JS rendering issues

- When you do need the DOM, playwright can handle a lot of the complexity out of the box: playwright will re-query the live DOM at action time and automatically wait for elements to populate. Libretto is also set up to pick selectors like data-testid, aria-label, role, id over class names or positional stuff that's likely to be dynamic.

- At the end of the day the files still live as code so you could always just throw a browser agent at it to handle a part of a workflow if nothing else works