Warp Terminal Goes Open Source Under AGPL-3.0 — 37,000 Stars, OpenAI as Founding Sponsor
Warp open-sourced its full client codebase under AGPL-3.0, with OpenAI as founding sponsor. The ~98% Rust repository hit 37,000 GitHub stars within days and landed #2 on trending, redefining the AI-native terminal as an open agentic development platform.
Warp opened its entire client codebase. After years as a venture-backed proprietary product — valued at $1.1B at its 2023 Series B — Warp published its full client under AGPL-3.0 with OpenAI named as founding sponsor of the repository.
The GitHub repository, warpdotdev/warp, crossed 37,000 stars within days of the release and peaked at #2 on GitHub trending.
What’s actually open source
The published codebase is approximately 98% Rust and includes:
- Terminal emulation layer
- Block-based UI system
- AI integration layer
- GraphQL communication layer
- Persistence and settings code
The underlying UI framework ships separately under the more permissive MIT license.
One thing stays closed: Oz, Warp’s cloud agent orchestration platform. Warp is betting that developers will contribute to and trust the client while the company retains the monetizable cloud layer — a familiar pattern from Elastic, HashiCorp before BUSL, and GitLab’s original open-core model.
OpenAI as founding sponsor
OpenAI’s name on the repository is not incidental. Warp natively supports Claude Code, OpenAI Codex, and Google Gemini CLI as first-class agent integrations. By placing OpenAI in the founding sponsor seat, Warp is signaling that the terminal is becoming a neutral runtime for AI coding agents — not a product tied to any single provider.
For OpenAI specifically, sponsoring the most developer-forward terminal in the market puts Codex in front of 700,000+ active Warp users as a default integration. That kind of distribution is worth more than the sponsorship cost.
Agent-first contribution model
Warp introduced an “agent-first contribution model” alongside the open-source launch. Contributors define specs for new features; AI agents — running natively inside Warp — write the implementation. Human review closes the loop.
This is not a marketing claim about how code will be written someday. Warp is using this model for its own contribution workflow now. Whether the open-source community adopts the same approach will tell us something real about how maintainer-facing AI tooling works at scale.
AGPL-3.0: the practical implication
AGPL-3.0 is a strong copyleft license. Any modifications to the Warp client that are distributed as a service must have their source published. This is a deliberate choice — it prevents commercial competitors from forking Warp’s codebase and shipping it as a closed product without contributing back.
For individual developers and organizations running Warp internally, AGPL-3.0 imposes no practical restrictions. The license only bites when you distribute a modified version.
The developer tooling space has been waiting for a terminal that takes AI seriously at the architecture level, not just as a feature bolt-on. Warp making that work open source — with 37,000 stars in days — suggests the market agrees it found one.