Puppeteer
Chrome DevTools Protocol automation library maintained by the Chrome team.
why this verdict
Keep it for the workflow, not the AI
Playwright and Browser Use cover the headline feature free, and the workflow around it is why you would still open this.
- A named launch, not a vibe named, unlinked
- Agent-native browser layers like Browser Use and Stagehand wrapping the low-level protocol away. OpenAI, October 22, 2025 — no announcement link recorded yet.
- How much of the job it covers headline only editorial call
- The headline feature, but not the workflow, data or integrations around it.
- Is there a free way to do it? yes
- 2 of 3 listed replacements have a usable free tier: Playwright and Browser Use.
- What the call is worth nothing to cancel
- No paid entry tier tracked, so there is no subscription to cancel.
- Threatened by
- OpenAI
- Since
- October 22, 2025
- List price
- free
- Per year
- —
The backstory
Puppeteer gave Node a clean handle on a headless Chrome instance and quietly became the engine under a generation of scrapers, PDF renderers and screenshot services. Its exposure is that it is now infrastructure rather than a choice: agent frameworks such as Browser Use and Stagehand wrap it, or wrap Playwright instead, and the developer never touches the protocol. It keeps the jobs where determinism matters more than flexibility, which is most of PDF and screenshot generation.
Escape hatches
Cross-browser support and a better testing story
playwright.dev open_in_newHosted headless browsers built for agent workloads
browserbase.com open_in_newAgent-first browser control from natural language
browser-use.com open_in_new2 of 3 replacements have a usable free tier.
