Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Libretto – Making AI browser automations deterministic

github.com

Post reply on HN
Print view View original

51–60 of 72 posts

Re: Show HN: Libretto – Making AI browser automations deterministic

#51

Post by terabytest »

Looks awesome, but I wonder if its functionality could be exposed to existing CLIs such as Claude Code instead of having to run it through its own CLI, mainly because I don't want to spend on credits when I've already got a CC subscription.

EDIT: To clarify, I realize there are skill files that can be used with Claude directly, but the snapshot analysis model seems to require a key. Any way to route that effort through Claude Code itself, such as for example exporting the raw snapshot to a file and instructing Claude Code to use a built-in subagent instead?

Re: Show HN: Libretto – Making AI browser automations deterministic

#52

Post by freedomben »

skapadia wrote: post #49

1. playwright-cli for exploration and ad-hoc scraping, in order to determine what works. 2. playwright code generation based on 1, which captures a repeatable workflow 3. agent skills - these can be playwright based, but in some cases if I can just rely on built-in tools like Web Search and Web Fetch, I will. playwright is one of the unsung heroes of agentic workflows. I heavily rely on it. In addition to the obvious…

Same playwright is phenomenal. You can also have the agent browse with MCP to figure out the workflow, then bang out a repeatable playwright script for it. It's a great combo

Re: Show HN: Libretto – Making AI browser automations deterministic

#54

Post by miohtama »

skapadia wrote: post #49

1. playwright-cli for exploration and ad-hoc scraping, in order to determine what works. 2. playwright code generation based on 1, which captures a repeatable workflow 3. agent skills - these can be playwright based, but in some cases if I can just rely on built-in tools like Web Search and Web Fetch, I will. playwright is one of the unsung heroes of agentic workflows. I heavily rely on it. In addition to the obvious…

You can also do Chrome MCP.

"Claude, reverse engineer the APIs of this website and build a client. Use Dev Tools."

I have succeed 8/8 websites with this.

Sites like Booking.com, Hotels.com, try to identify real humans with their AWS solution and Cloudflare, but you can just solve the captcha yourself, login and the session is in disguishable from a human. Playwright is detected and often blocked.

Re: Show HN: Libretto – Making AI browser automations deterministic

#56

Post by drob518 »

potter098 wrote: post #48

[flagged]

And even beyond a week. What happens when the site owner redesigns the interface and breaks things? What is the recovery process and how “deep” does the rework have to go? Would you expect to use the same prompt and just have the AI figure it out again and then ship the new code?

Re: Show HN: Libretto – Making AI browser automations deterministic

#60

Post by muchael »

skapadia wrote: post #49

1. playwright-cli for exploration and ad-hoc scraping, in order to determine what works. 2. playwright code generation based on 1, which captures a repeatable workflow 3. agent skills - these can be playwright based, but in some cases if I can just rely on built-in tools like Web Search and Web Fetch, I will. playwright is one of the unsung heroes of agentic workflows. I heavily rely on it. In addition to the obvious…

Agreed! One thing that we felt was missing from the existing MCP tools was user recording. For old and shitty healthcare websites it's easier to just show the workflow than explain it

The playwright codegen tool exists, but the script it generates is super simple and it can't handle loops or data extraction.

So for libretto we often use a mix of instructions + recording my actions for the agent. Makes the process faster than just relying on a description and waiting for the agent to figure out the whole flow

Post reply on HN