Warp opens docs repo after 285 Oz agents migrated its CMS in 3 hours
Warp open-sourced its documentation after moving from a CMS to a GitHub Markdown repo with Astro, with a 3-hour proof of concept and 285 Oz cloud agents handling most of the migration. It matters because the docs now behave like code that both contributors and agents can inspect, patch, and reuse directly.
TL;DR
- Warp said it has open-sourced its docs after moving from a CMS to a GitHub Markdown repo with Astro, and warpdotdev's announcement says the proof of concept took three hours.
- According to warpdotdev's migration thread, Hong Yi launched 285 Oz cloud agents in parallel to migrate chunks of the site and verify the output with computer use.
- Warp's docs repo is already live at warpdotdev/docs, where the public repository shows an MDX-heavy stack built with Astro and released under MIT, while the launch post frames the move as part of Warp's broader open source push.
- The interesting bit in warpdotdev's follow-up post is not just docs-as-code, but that community members can change layout, sidebar shape, and how agents consume the content instead of editing through a locked CMS.
You can read Warp's migration write-up, browse the new docs repository, and cross-check Warp's earlier open source workflow note, where the company said Oz already does most of the implementation work on approved issues. The detail that sticks is the 285-agent migration count, plus Warp's claim in its docs-as-code thread that the real win is exposing structure that both humans and agents can patch.
Astro repo
Warp moved its documentation from a CMS into a GitHub repo of Markdown and MDX built on Astro and Starlight, according to warpdotdev's launch post and the public warpdotdev/docs repository. The repo describes itself as the source for docs.warp.dev, lists MDX as the primary language, and exposes the site code under MIT.
That makes the docs stack inspectable in the same way the product repo is inspectable. Warp's blog post says the proof of concept took three hours, which is a very fast signal that the migration was more about restructuring ownership than rebuilding the site from scratch.
Oz agents
Most of the migration work was not done by hand. In warpdotdev's thread, Warp says Hong Yi kicked off 285 Oz cloud agents in parallel, each handling a chunk of the docs site and verifying its work with computer use.
Warp's earlier open source discussion describes the same division of labor on the product side: Oz does most of the implementation heavy lifting, the community helps verify, and Warp reviews and ships. Warp's separate computer use post says those verification runs rely on specialized GUI-driving subagents, which helps explain how the docs migration could include browser-level checks instead of just static file conversion.
Control surface
Warp's clearest argument for the move is in its docs-as-code post: open docs let contributors change more than prose.
- Page layout
- Sidebar structure
- Content format in the repo
- How agents consume the content
That is a more specific claim than the usual "docs are now on GitHub" announcement. Warp is treating documentation as part of the product surface, not just as support material.
OpenWarp fork
A fork showed up almost immediately. dingyi's post linked to zerx-lab/warp, an OpenWarp fork that positions itself as a free and open source Warp variant.
That does not tell us much yet about adoption, but it does show how quickly Warp's new open source posture is turning into derivative projects. Opening the docs repo and the client repo in the same stretch means the forkable surface now includes both the product and the documentation around it.