Warp has open-sourced the Warp terminal client. The repo went live on GitHub on April 28, 2026 under the Apache-2.0 license and accumulated roughly 26,000 stars within hours, with the team merging community PRs from day one. OpenAI is the founding sponsor of the open-source repository, and the agentic management workflows in the open release are powered by GPT models.
The scope of the open-sourcing is precise. The terminal client — block-based navigation, IDE-like input, vertical tabs, native code review, rich input, remote control — is fully open. So is universal agent support: Warp now drives Claude Code, Codex, Gemini CLI, OpenCode, and other CLI coding agents with notifications and orchestration UI on top. The closed piece is Oz, Warp's cloud agent orchestration platform, which runs multiple coding agents in parallel in the cloud with full visibility and control. That stays proprietary and remains the commercial product.
The strategic logic is clear. Warp had previously kept the terminal proprietary specifically to avoid being forked by competitors. Open-sourcing now reflects a bet that the durable moat is in cloud agent orchestration, not in the terminal UX itself — and that owning the de facto open agentic terminal is worth more than defending the closed one. It also blunts the competitive threat from Cursor, Zed, and the rising tide of agent-native CLI environments by removing the 'closed source' line of attack.
The community fit is good. Terminal users are exactly the population most likely to value Apache-2.0 tooling, run local agents, and contribute back. The 26K-stars-in-hours number suggests real pent-up demand. The open question is whether Oz can keep enough orchestration value above the open terminal to sustain Warp's commercial business — the same question that has dogged every open-core company that came before it.