Stagehand 2.0 vs Plain

“The primitive here is clean: a typed TypeScript API over Playwright that swaps selector-based targeting for vision + LLM reasoning, so your automation doesn't break the moment a designer changes a class name. The DX bet is to put the complexity in the model call, not the selector string — and that's the right call because selector maintenance is the silent killer of every Playwright test suite I've ever inherited. First 10 minutes you run `npx create-stagehand` and you're issuing natural language `act()` calls against a real browser; that's a fast hello-world that earns trust. The weekend-alternative comparison is real — you could wrap Playwright with a GPT-4V call yourself — but parallel session management and the hosted cloud are the parts that would take you a week, not an afternoon, and that's where the ship decision lands.”

“The `.claude/rules/` integration and typed APIs are exactly what you want when you're letting agents modify your codebase. OTel built-in is a legitimate win — no more strapping on tracing as an afterthought. If you're starting a new Python project in 2026, Plain is worth serious consideration.”

“Direct competitors are Playwright MCP, Puppeteer AI wrappers, and Browser Use — the space is genuinely crowded. The scenario where Stagehand breaks is multi-step authenticated workflows on SPAs with aggressive anti-bot fingerprinting; vision-based detection is still fooled by CAPTCHAs and shadow DOM chaos in ways that selector-based tools handle with explicit waits. What kills this in 12 months is not a competitor — it's Anthropic or OpenAI shipping computer-use as a managed API that makes the browser layer someone else's problem, collapsing the value prop. The thing that saves it is the open-source flywheel: if the community builds enough adapters and the cloud pricing stays rational, Browserbase has a distribution moat that pure API players won't have on day one of their browser product.”

“Django's 'magic' is also its ecosystem — 20 years of packages, tutorials, and institutional knowledge. Plain's ecosystem is tiny. For any non-trivial project, you'll hit the ecosystem wall fast. 'Designed for agents' is a compelling narrative but the migration cost from Django is real and steep.”

“The buyer is an engineering team building a product that needs web data or web actions at scale — this comes out of infrastructure budget, not a tool subscription, and that's a healthy budget to be in. The pricing architecture is smart: open source drives developer adoption and the hosted cloud is where the margin lives, which means Browserbase doesn't have to convince anyone to pay until the user is already dependent on the primitive. The moat question is real though — the cloud environment is defensible only if the reliability and session management are meaningfully better than self-hosting, and that claim needs to be proven in production, not on a landing page. If Anthropic's computer-use API matures and AWS wraps it in a managed service, the hosted layer commoditizes fast; the open-source repo and developer mindshare are the only durable assets here.”

“The job-to-be-done is singular and well-scoped: automate browser interactions without maintaining selectors, at a scale that requires parallel sessions and cloud infrastructure. Onboarding hits value fast — the `create-stagehand` CLI and the `act()` / `extract()` / `observe()` three-verb API mean a developer can run a working agent in under five minutes without reading architecture docs. The product is opinionated in the right place: it hides selector complexity and surfaces only the natural language intent, which is exactly where the opinion should sit. The completeness gap is the observability layer — when an agent fails mid-workflow you need to know why, and the current tooling for debugging vision-based failures is immature enough that teams will keep a Playwright fallback around, which is the dual-wielding smell I don't like in an otherwise focused product.”

“The question 'is this codebase understandable to an AI agent?' is going to be central to framework design by 2027. Plain is three years ahead of that conversation. Frameworks that don't add agent-readability features will be retrofitting them later at significant cost.”

“As someone who ships products, not just writes code, I care about the full stack being coherent. Plain's opinionated structure means less time arbitrating between packages and more time building. The built-in OTel means I can debug AI-assisted changes without adding another tool.”