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
FL score
out of 100
Verdict
high confidence
Competition
14
competitors found, emerging market, funded players
Trend
No signal yet
Libretto aims to make AI browser automations deterministic and debuggable by generating inspectable code at development-time, targeting complex, high-stakes enterprise environments.
The pain
The gap
Build angle
Strengths
Questions about this idea?
FlyBot reads the scoring and gives you a second opinion on “Libretto – Making AI browser automations deterministic”.
Risks
Next steps
Fly Labs Method
Is the pain real, is there a gap, is it the right time, can one person build it.
The idea targets a real, severe pain point in high-stakes browser automation by offering a deterministic, code-based approach, creating a clear gap in a crowded market. However, the technical complexity for a solo builder and the potential for a slow ramp-up in other niches are notable challenges.
Value Equation
Dream outcome and how likely it feels, against the time and effort it costs.
This idea has strong market viability and a clear value proposition for reliability in a growing market, but faces challenges in execution and building a defensible offer as a solo endeavor.
One-Person Business
Curiosity pull, identity fit, and a path from free value to paid for a solo creator.
A strong problem clarity and founder experience, but hindered by the technical complexity, niche audience reach, and the project's inherent lack of simplicity for a solo builder.
Viral Frameworks
Hook strength, shareability, and how cheaply it can be tested.
Strong value proposition and specific audience, but needs robust validation beyond initial use cases and faces challenges in distribution and inherent technical complexity for a solo builder.
Builder Lens
Evidence the problem exists, timing, defensibility, and a model that fits on a napkin.
Strong demand for reliable automation with a clear, differentiated approach to solve a persistent, costly problem, though the MVP must be carefully scoped for rapid adoption.
Why this verdict
Five lenses, one composite. How scoring works
The angle
This weekend
Who is already there, emerging market
An open-source Node.js-based automation framework for end-to-end testing across Chromium, Firefox, and WebKit.
Pricing: Free and open-source.
A long-established open-source framework for automating web browsers, supporting a wide range of browsers and programming languages.
Pricing: Free and open-source.
An open-source automation tool for web app testing that runs tests directly in the browser, focusing on developer experience and fast feedback.
Pricing: Free and open-source, with a paid Cypress Cloud for parallelization and advanced features.
A Node.js library developed by Google that provides a high-level API to control headless or full Chrome/Chromium browsers.
Pricing: Free and open-source.
An AI-powered test automation platform that uses artificial intelligence to speed up the authoring, execution, and maintenance of automated tests.
Pricing: Not publicly available, often enterprise-focused. Reviewers compare it with Autify on cost and features.
An AI-powered software testing automation platform that allows users to create and maintain automated tests without coding, and self-heals tests.
Pricing: Not publicly available, enterprise-focused. Reviewers compare it with Testim on cost and features.
A robotic process automation (RPA) software that provides tools for automating various business processes, including browser automations.
Pricing: Offers various plans, including a free trial and enterprise pricing. Specific details are not easily found without contacting sales.
An RPA platform that provides intelligent automation solutions, including AI-powered bots for automating business and browser tasks.
Pricing: Not publicly available, enterprise-focused.
A service that helps create automated workflows between favorite apps and services to synchronize files, get notifications, collect data, and more.
Pricing: Included with some Microsoft 365 plans; standalone plans start around $15/user/month for basic, with higher tiers for more advanced features.
A web-based service that allows end users to integrate the web applications they use and automate workflows.
Pricing: Free plan (100 tasks/month), Professional ($29.99/month for 750 tasks, billed monthly), Team ($103.50/month for 2,000 tasks, billed monthly), Enterprise (custom pricing). Prices scale with task usage.
A visual platform for connecting apps and automating workflows, often positioned as a more powerful and cost-effective alternative to Zapier.
Pricing: Free plan (1,000 operations/month), Core ($10.59/month for 10,000 operations, billed annually), Pro ($18.82/month for 10,000 operations, billed annually), Teams ($34.12/month for 10,000 operations, billed annually). Operations are counted per action.
An open-source library that allows AI agents to control web browsers autonomously using LLMs to understand tasks and perform actions.
Pricing: Open-source with free and paid tiers (e.g., $30/month for pro-versions), plus LLM costs.
What they charge
Recent news
PxlPeak, February 26 2026
ScrapeGraphAI, February 12 2026
Firecrawl, February 28 2026
BrowserStack, January 15 2026
Sauce Labs, January 28 2026
Market signals
The AI browser automation market is growing, with a shift towards AI-powered, low-code/no-code solutions that offer self-healing tests and easier maintenance. Recent funding rounds indicate strong investor interest in companies that provide intelligent automation and testing platforms. The market includes both established open-source frameworks and newer AI-native tools.
What frustrates people
Last summer we faced a conundrum at my company, Tiger Data, a Postgres cloud vendor whose main business is in timeseries data. We were trying to grow our business towards emerging AI-centric workloads and wanted to provide a state-of-the-art hybrid search stack in Postgres. We'd already built pgvectorscale in house with the goal of scaling semantic search beyond pgvector's main memory limitations. We just needed a scalable ranked keyword search solution too.The problem: core Postgres doesn't provide this; the leading Postgres BM25 extension, ParadeDB, is guarded behind AGPL; developing our own extension appeared daunting. We'd need a small team of sharp engineers and 6-12 months, I figured. And we'd probably still fall short of the performance of a mature system like Parade/Tantivy.Or would we? I'd be experimenting long enough with AI-boosted development at that point to realize that with the latest tools (Claude Code + Opus) and an experienced hand (I've been working in database systems internals for 25 years now), the old time estimates pretty much go out the window.I told our CTO I thought I could solo the project in one quarter. This raised some eyebrows.It did take a little more time than that (two quarters), and we got some real help from the community (amazing!) after open-sourcing the pre-release. But I'm thrilled/exhausted today to share that pg_textsearch v1.0 is freely available via open source (Postgres license), on Tiger Data cloud, and hopefully soon, a hyperscalar near you:https://github.com/timescale/pg_textsearchIn the blog post accompanying the release, I overview the architecture and present benchmark results using MS-MARCO. To my surprise, we were not only able to meet Parade/Tantivy's query performance, but exceed it substantially, measuring a 4.7x advantage on query throughput at scale:https://www.tigerdata.com/blog/pg-textsearch-bm25-fu
AI
Hi HN!I recently switched from a Fedora/GNOME laptop to a MacBook Air. My old setup served me well as a portable workstation, but I’ve started traveling more while working remotely and needed something with similar performance but better battery life. The main thing I missed was a simple taskbar that shows the windows in the current workspace instead of a Dock that mixes everything together.I built boringBar so I would not have to use the Dock. It shows only the windows in the current Space, lets you switch Spaces by scrolling on the bar, and adds a desktop switcher so you can jump directly to any Space. You can also hide the system Dock, pin apps, preview windows with thumbnails, and launch apps from a searchable menu (I keep Spotlight disabled because for some reason it uses a lot of system resources on my machine).I’ve been dogfooding it for a few months now, and it finally felt polished enough to share.It’s for people who like macOS but want window management to feel a bit more like GNOME, Windows, or a traditional taskbar. It’s also for people like me who wanted an easier transition to macOS, especially now that Windows feels increasingly user-hostile.I’d love feedback on the UX, bugs, and whether this solves the same Dock/Spaces pain for anyone else.P.S. It might also appeal to people who feel nostalgic for the GNOME 2 desktop of yore. I started my Linux journey with it, and boringBar brings back some of that feeling for me.
AI
### Describe the project you are working on Godot C# bindings ### Describe the problem or limitation you are having in your project For the past weeks, I've been discussing with several Unity users intending to move to Godot C# regarding dealing with the C# garbage collector. The most common complaint I hear from users is that, in Unity, allocations can trigger unexpected GC spikes into the game. In Godot, we target to make all of the high performance APIs (those that intended to be called every frame) not allocate any memory, so theoretically the GC should not be a problem. Additionally, Godot starting from 4.0, uses the Microsoft CoreCLR version of .net, which also supposedly has a better garbage collector than Unity. But in all, after several discussions with Unity users, neither is enough reassurance for them, and they would really feel safer if Godot exposed a zero allocation API. ### Describe the feature / enhancement and how it helps to overcome the problem or limitation The idea of this proposal is that Godot exposes zero allocation versions of many functions in the C# API, that users can use if they desire. Technically, this could be done from the binding generator itself, without breaking compatibility, and without doing any modification to Godot itself. ### Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams **WARNING** I am not familiar with C#, so take this as pseudocode. Imagine you have two functions exposed as to C#: ```C# void MyClass.SetArray( Vector2[] array); Vector2[] MyClass.GetArray(); ``` This works and is pretty and intuitive. However, it has two problems: * GC is allocated on return * Memory is copied to Godot native formats every time there is a call. The idea is to add NoAlloc versions, which can be generated directly by the binder automatically when required: ```C# void MyClass.SetArrayNoAlloc( Godot.Collections.PackedVector2Array array); void MyCl
AI