← Back to Product Feed

Hacker News Show HN: Libretto – Making AI browser automations deterministic

A solution for generating and debugging reliable browser automations using "development-time AI" to produce inspectable code, contrasting with unreliable, expensive, and opaque "runtime AI" agents, particularly for complex, high-stakes environments like healthcare.

118
Traction Score
46
Discussions
Apr 16, 2026
Launch Date
View Origin Link

Product Positioning & Context

AI Executive Synthesis
A solution for generating and debugging reliable browser automations using "development-time AI" to produce inspectable code, contrasting with unreliable, expensive, and opaque "runtime AI" agents, particularly for complex, high-stakes environments like healthcare.
Libretto addresses a critical reliability and governance challenge in AI-driven browser automation, particularly in high-stakes enterprise contexts like healthcare. By shifting from "runtime AI" to "development-time AI," it generates inspectable, deterministic code, mitigating the risks of opaque, unpredictable agent behavior. This approach directly tackles the unreliability and cost issues associated with dynamic DOM parsing and excessive AI calls. The hybrid Playwright/network request strategy enhances robustness and bot detection evasion. Libretto's focus on code ownership, debugging, and adherence to existing coding conventions positions it as a superior solution for enterprises requiring auditable, maintainable, and reliable automation, contrasting sharply with black-box runtime agent solutions.
Libretto (https://libretto.sh) is a Skill+CLI that makes it easy for your coding agent to generate deterministic browser automations and debug existing ones. Key shift is going from “give an agent a prompt at runtime and hope it figures things out” to: “Use coding agents to generate real scripts you can inspect, run, and debug”.Here’s a demo: https://www.youtube.com/watch?v=0cDpIntmHAM. Docs start at https://libretto.sh/docs/get-started/introduction.We spent a year building and maintaining browser automations for EHR and payer portal integrations at our healthcare startup. Building these automations and debugging failed ones was incredibly time-consuming.There’s lots of tools that use runtime AI like Browseruse and Stagehand which we tried, but (1) they’re reliant on custom DOM parsing that's unreliable on older and complicated websites (including all of healthcare). Using a website’s internal network calls is faster and more reliable when possible. (2) They can be expensive since they rely on lots of AI calls and for workflows with complicated logic you can’t always rely on caching actions to make sure it will work. (3) They’re at runtime so it’s not interpretable what the agent is going to do. You kind of hope you prompted it correctly to do the right thing, but legacy workflows are often unintuitive and inconsistent across sites so you can’t trust an agent to just figure it out at runtime. (4) They don’t really help you generate new automations or help you debug automation failures.We wanted a way to reliably generate and maintain browser automations in messy, high-stakes environments, without relying on fragile runtime agents.Libretto is different because instead of runtime agents it uses “development-time AI”: scripts are generated ahead of time as actual code you can read and control, not opaque agent behavior at runtime. Instead of a black box, you own the code and can inspect, modify, version, and debug everything.Rather than relying on runtime DOM parsing, Libretto takes a hybrid approach combining Playwright UI automation with direct network/API requests within the browser session for better reliability and bot detection evasion.It records manual user actions to help agents generate and update scripts, supports step-through debugging, has an optional read-only mode to prevent agents from accidentally submitting or modifying data, and generates code that follows all the abstractions and conventions you have already in your coding repo.Would love to hear how others are building and maintaining browser automations in practice, and any feedback on the approach we’ve taken here.
Skill+CLI coding agent deterministic browser automations development-time AI runtime AI EHR and payer portal integrations Browseruse Stagehand

Related Ecosystem & Alternatives

Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.

Deep-Dive FAQs

What is Libretto – Making AI browser automations deterministic?
Libretto – Making AI browser automations deterministic is analyzed by our AI as: A solution for generating and debugging reliable browser automations using "development-time AI" to produce inspectable code, contrasting with unreliable, expensive, and opaque "runtime AI" agents, particularly for complex, high-stakes environments like healthcare.. It focuses on Libretto addresses a critical reliability and governance challenge in AI-driven browser automation, particularly in high-stakes enterprise contexts...
Where did Libretto – Making AI browser automations deterministic originate?
Data for Libretto – Making AI browser automations deterministic was aggregated directly from the Hacker News community ecosystem, representing raw developer and early-adopter sentiment.
When was Libretto – Making AI browser automations deterministic publicly launched?
The initial public indexing or launch date for Libretto – Making AI browser automations deterministic within our tracked developer communities was recorded on April 16, 2026.
How popular is Libretto – Making AI browser automations deterministic?
Libretto – Making AI browser automations deterministic has achieved measurable traction, logging over 118 traction score and facilitating 46 recorded discussions or engagements.
Which technical categories define Libretto – Making AI browser automations deterministic?
Based on metadata extraction, Libretto – Making AI browser automations deterministic is categorized under topics such as: Skill+CLI, coding agent, deterministic browser automations, development-time AI.
What are some commercial alternatives to Libretto – Making AI browser automations deterministic?
Our semantic intelligence engine identifies potential commercial alternatives in the SaaS space, such as Google AI Edge Eloquent, which offers overlapping value propositions.
How does the creator describe Libretto – Making AI browser automations deterministic?
The original author or development team describes the product as follows: "Libretto (https://libretto.sh) is a Skill+CLI that makes it easy for your coding agent to generate deterministic browser automations and debug existing ones. Key shift is going from “give an agent ..."

Community Voice & Feedback

jimmypk • Apr 16, 2026
The 'deterministic' framing is the part I'd want to understand better. When a model generates a Playwright script, selector choice is often the fragile element: LLMs frequently generate CSS class selectors or XPath rather than Playwright's recommended getByRole/getByLabel/getByText approach, even when accessible-name selectors would work. The generated code can 'work' on first run but break on the first layout tweak.@muchael: does Libretto constrain the model to prefer accessible-name-based selectors during generation, or does the determinism come primarily from the execution-verification loop (run → fail → self-correct)? The two approaches have meaningfully different failure modes—the first makes the initial code robust, the second only catches brittleness at runtime.
cowartc • Apr 16, 2026
This is what I found doing playwright based extraction against anti-bot defenses. Runtime agents were brittle. It felt like trying to debug/audit a black box.We used to deal with RPA stuff at work. Always fragile. Good to see evolution in the space.
Guillaume86 • Apr 16, 2026
Did you consider MCP sampling to avoid requiring your own LLM access? (for the clients that support it of course, but I think it's important and will become standard anyway)
terabytest • Apr 16, 2026
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?
skapadia • Apr 16, 2026
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 workflow3. 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 DOM inspection capabilities, the fact that the console and network can be inspected is a game changer for debugging. watching an agent get rapid feedback or do live TDD is one of the most satisfying things ever.Browser automation and being able to record the graphics buffer as video, during a run, open up many possibilities.
potter098 • Apr 16, 2026
The interesting part to me is recovery after the first generated script goes stale. I’d be curious whether you measure success as 'initial generation works' or 'the same flow still passes after small DOM/layout changes a week later', since that seems like the boundary between a neat demo and something a team can rely on.
admiralrohan • Apr 16, 2026
Very interesting idea. Old school solutions but with new methods.
But maybe we can't make everything deterministic for complex cases, the scenarios that opened after LLM arrived into scene. Maybe we need a mix of both.
coderw • Apr 16, 2026
Curious how you handle target site changes - does the agent get triggered to regenerate, or do you just wait for the script to fail in prod first?
anthuswilliams • Apr 15, 2026
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.
z3ugma • Apr 15, 2026
Love it! Do you have a BAA with Claude though? Otherwise, your demo is likely exposing PHI to 3rd parties and exposing you to risk related to HIPAA

Discovery Source

Hacker News Hacker News

Aggregated via automated community intelligence tracking.

Tech Stack Dependencies

No direct open-source NPM package mentions detected in the product documentation.

Media Tractions & Mentions

No mainstream media stories specifically mentioning this product name have been intercepted yet.

Deep Research & Science

No direct peer-reviewed scientific literature matched with this product's architecture.