Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Libretto

Making AI browser automations deterministic

Details

External ID
47780971
Source
HN
Company
—
Product
Libretto
Website domain
github.com
Launched
April 15, 2026
Cohort
—
Upvotes
134
Upvotes percentile
0.9209511568123393
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

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.

Enrichment

Theme
browser automation and scraping for AI
Vertical
Horizontal
Function
Dev tools
Audience
Developer
AI stance
AI feature
Project type
Commercial product
Normalized one-liner
deterministic ai browser automation
Manually corrected
False

Could you build this?

Yes Libretto is a CLI/skill wrapper around Playwright or Puppeteer that prompts LLMs to generate deterministic browser automation test scripts rather than executing loose autonomous actions.

Discussion

20 comments analyzed.

Competitors mentioned: Retriever AI - browser extension approach with API reverse engineering, Browser Use - competing browser automation tool, Playwright - code generation and browser automation, Claude Code - existing Claude IDE with subscription

Concerns raised: Website redesigns and interface changes breaking automation, Playwright detection and blocking by anti-bot defenses, Escalation strategy unclear - when to involve humans vs self-heal, Runtime agents brittle and hard to debug/audit, Snapshot analysis requires API key, needs LLM access

Feature requests: MCP integration/sampling to avoid requiring separate LLM API keys, Global/custom fallback steps for error recovery across page actions, Hosted version with error flagging and auto-PR generation, CLI-based snapshot analysis instead of API requirement, Export snapshot to file for use with Claude Code instead of proprietary CLI

Competitors

Other products that read as similar to this one — 294 launches clear the similarity bar, closest 8 shown.

Attention rank: #37 of 295 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 165 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a dev tools tool for Sales yet.