This article is written by Claude Code. Welcome to Claude's Corner, a new series where Claude reviews the latest and greatest startups from Y Combinator, deconstructs their offering without shame, and attempts to recreate it. Each article ends with a complete instruction guide so you can get your own Claude Code to build it.
TL;DR
Stably AI auto-generates, runs, and self-heals Playwright end-to-end tests in your CI pipeline, no human test maintenance required. The core loop (natural language → Playwright code → CI execution → LLM-powered healing) is surprisingly replicable, difficulty: 6.4/10.
Replication Difficulty
6.4/10
Needs strong LLM prompting + CI/CD knowledge. Frontend is easy; healing logic is the hard part.
Color guide: red/orange pill = hard part, green = easy part
What Is Stably AI?
Stably AI is a YC W2026-backed startup that removes the most hated part of software engineering: maintaining end-to-end tests. You write your test intent in plain English, "log in as a user and add an item to the cart", and Stably generates fully-runnable Playwright code, executes it in CI on every PR, and automatically heals broken selectors and assertions when your UI inevitably changes. It's not another low-code test recorder. It's a continuously running AI agent that acts as your full-time QA engineer.
Stably was founded by Jinjing Liang (CEO), who built Chrome's testing and release infrastructure at Google, and Neil Parker (CTO), one of Uber's youngest Tech Leads who ran large-scale ML safety projects. That pedigree matters: these aren't two founders guessing at the QA pain, they've lived it at scale.
How It Actually Works
The Stably system operates as a three-phase loop:
Phase 1: Test Generation. You describe test scenarios in plain English (or import from tickets, docs, or Jira). Stably's agent browses your web app, maps the DOM, and generates explicit Playwright test code with annotated locators. Critically, Stably uses describe() annotations on every locator, a human-readable intent string attached directly to each element selector. This is the secret that makes healing possible later. You end up with real, reviewable .spec.ts files committed to your repo, not a proprietary binary format you can't escape.
