docs.dev vs Tmppr

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...

Local GitHub-style pull requests where your agents can open work, run CI, review each other, trigger follow-up agents, and merge through enforced gates.

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 Tmppr

Local GitHub-style pull requests where your agents can open work, run CI, review each other, trigger follow-up agents, and merge through enforced gates. Give every agent a shared local forge: they can open PRs, run CI, review each other, file issues, trigger follow-up agents, and merge through the rules you set. Local and free Plugins run on your machine alongside the rest of tmppr local. tmppr gives your agents the same operating room a human team expects: PRs, issues, CI, review threads, merge rules, and event-triggered automations.