Warp Goes Open Source. The Real Product Is Oz
Warp just open-sourced its terminal. Five years of Rust code, AGPLv3 plus MIT for the UI crates, dropped on GitHub on April 28. Within a day the repo crossed 38,000 stars. OpenAI is the founding sponsor and is paying the bill for GPT models powering the contribution flow.
But here is the move that actually matters. The thing Warp open-sourced is the client. The thing Warp is selling is Oz, a cloud agent platform that triages issues, asks clarifying questions, writes code, opens pull requests, and ships them. The community direction-sets, Oz implements. Warp is calling this Open Agentic Development. In plain language: humans say what to build, agents do the building, and you can watch every session in the open.
This flips the open source playbook on its head. Used to be that going open source meant inviting community contributions because typing code is the bottleneck. With Oz, typing code is the cheapest part. The bottleneck is direction, taste, verification. So Warp gave away the part that agents can rewrite for you, and kept the part that orchestrates them. Cursor, Codex, Claude Code, Windsurf β none of them have published an open-source client. Warp is testing whether owning the harness for community-driven agentic contribution is the new moat.
The near-million-developer userbase Warp claims gives them a head start. Whether the AGPLv3 tax actually deters competitors copying the client, and whether Oz is sticky enough to convert that flow into revenue, those are the open questions. But the architectural bet is clean: client is a commodity, the orchestration layer is the product. If this works, expect every coding agent company to ship an open client and a closed cloud agent runtime within six months.
Link: https://www.warp.dev/blog/warp-is-now-open-source
← Back to all articles
But here is the move that actually matters. The thing Warp open-sourced is the client. The thing Warp is selling is Oz, a cloud agent platform that triages issues, asks clarifying questions, writes code, opens pull requests, and ships them. The community direction-sets, Oz implements. Warp is calling this Open Agentic Development. In plain language: humans say what to build, agents do the building, and you can watch every session in the open.
This flips the open source playbook on its head. Used to be that going open source meant inviting community contributions because typing code is the bottleneck. With Oz, typing code is the cheapest part. The bottleneck is direction, taste, verification. So Warp gave away the part that agents can rewrite for you, and kept the part that orchestrates them. Cursor, Codex, Claude Code, Windsurf β none of them have published an open-source client. Warp is testing whether owning the harness for community-driven agentic contribution is the new moat.
The near-million-developer userbase Warp claims gives them a head start. Whether the AGPLv3 tax actually deters competitors copying the client, and whether Oz is sticky enough to convert that flow into revenue, those are the open questions. But the architectural bet is clean: client is a commodity, the orchestration layer is the product. If this works, expect every coding agent company to ship an open client and a closed cloud agent runtime within six months.
Link: https://www.warp.dev/blog/warp-is-now-open-source
Comments