Today we are announcing a fundamental change in how we build Warp: the Warp client is now open-source, and the community can participate in building it using an agent-first workflow managed by Oz , our cloud agent orchestration platform. OpenAI is the founding sponsor of the new, open‑source Warp repository , and the new agentic management workflows are powered by GPT models .
Open-sourcing with an agent-powered repo is our vision of how software will be built in the future. Humans managing agents at scale to build production-grade software is the model, and implementing this model in the open will allow software to improve most quickly.
Put simply: we believe that a diverse collection of contributors with unique ideas + Oz agents with structured processes + a rich corpus of context and self-improvement loops will yield a magic product, beyond what we might build internally.
The primary reason is that we think we can ship a better Warp, more quickly, if we open source and work with our community to help supervise a fleet of agents. The biggest bottleneck to development is no longer writing code – it’s all the human-in-the-loop activities around the code: speccing the product and verifying behavior, and frankly, we are limited in what our internal team can do and the pace we want to move at.
We’ve found that agents can handle the implementation heavy lifting really well. That frees contributors to focus on the higher-leverage work: shaping what gets built and making sure it’s right.
Inviting our community into the process to help manage agents will be a big unlock. We now have a lot of confidence in code that is generated by Oz with our rules, context and verification, so anyone contributing should have a high chance of success coding a feature correctly. Moreover, leaning on agents creates pressure for us to nail orchestration, memory, handoff, and all of the other parts of agentic engineering that are core to our business. There’s a virtuous loop here.