Warp, the AI-powered terminal and development environment built in Rust, has open-sourced its client codebase on GitHub after five years as a closed-source product. The licensing is split: UI framework crates are MIT-licensed, and everything else falls under AGPL v3.
OpenAI is the founding sponsor, and agentic workflows are powered by GPT models through Warp’s proprietary cloud platform, called Oz. That detail matters more than it might seem at first glance.
<h2>What’s actually open and what isn’t</h2>
The client code is on GitHub and accepts community contributions. But the recommended contribution workflow runs through Oz, Warp’s own agent orchestration platform. The vision Warp is selling is that contributors focus on ideas, specs, and review while AI agents handle implementation — a “human manages agents” model rather than traditional open-source collaboration.
AI features still depend on Warp’s backend, and bring-your-own-key model freedom is locked behind paid plans. Within days of the release, the community forked the project as OpenWarp specifically to enable any OpenAI-compatible endpoint without those restrictions.
Warp does support third-party CLI agents — Claude Code, Codex, Gemini CLI — alongside its built-in coding agent. The release also adds support for Kimi, MiniMax, and Qwen models, an “auto (open)” routing option for intelligent task assignment, deeper UI customization, and a programmatic settings file.
<h2>The competitive logic</h2>
CEO Zach Lloyd has been straightforward that this is a business strategy, not a philosophical shift. Warp is up against well-funded closed-source rivals, and going open source is a way to accelerate development through community involvement and attract developers who won’t touch proprietary tools.
The timing is notable. Roo Code recently sunset, and Cursor was acquired. The developer tooling space is consolidating fast, and Warp is making a land grab while there’s still room to move.
The underlying technical stack is Rust, using Tokio, Alacritty, and related crates. The architecture is solid. The question is whether the open-source label holds up when the most useful parts — the agentic workflows, the model routing, the backend infrastructure — remain firmly under Warp’s control.
For developers who want genuine model agnosticism and no dependency on a vendor’s cloud platform, the AGPL license and the OpenWarp fork are worth watching. For everyone else, Warp’s bet is that the combination of open client code and proprietary AI infrastructure is good enough to win.

Collections

Warp, the Rust-based AI terminal, has open-sourced its client code under a split license: MIT for UI framework crates and AGPL v3 for everything else. OpenAI is the founding sponsor, and agentic workflows run through Warp's proprietary cloud platform Oz. Key limitations include AI features still depending on Warp's backend, with bring-your-own-key model freedom locked behind paid plans. The community has already forked the project as OpenWarp to enable unrestricted OpenAI-compatible endpoints. CEO Zach Lloyd frames this as a competitive business move rather than a philosophical shift, aiming to attract developers who avoid proprietary tools while the developer tooling space consolidates rapidly following Roo Code's sunset and Cursor's acquisition.

Warp terminal goes open-source under AGPL, with OpenAI as founding sponsor

Now we are just waiting for the fork that allows for local or private models to be used.

I installed it to play with it around, but claude sonnet and opus is only usable with “premium”-subscription, so i removed it instantly without testing again. This is not open source software!

Excelente noticia yo la uso y es muy buena.

This is a great step towards reliability 🥳