docs.dev vs Libretto PR agents

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no...

Automatically investigate failing Playwright scripts against the live page and open a GitHub pull request with a proposed fix.

About docs.dev

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no platform fee, no metered AI. Reviews, branches, and rollbacks come free, because it is just git. Your content in their database, and an export button you hope works when you leave. Writing AI is the agent you already have; reader-facing AI runs on your Workers AI.

About Libretto PR agents

Automatically investigate failing Playwright scripts against the live page and open a GitHub pull request with a proposed fix. The PR agent starts only after a failure, when it can investigate what changed and propose a fix. Run locally, in your own infrastructure, or with a hosted browser provider. The PR agent focuses on diagnosing the failure and proposing a code fix for future runs. Your existing catch, retry, fallback, and error handling remain responsible for the current run, while the agent opens a pull request when it finds a fix.