Warp's terminal is now open source. The cloud agent platform Oz is the actual product.

Warp open-sourced its agentic terminal client on Tuesday. The repo at github.com/warpdotdev/warp ships under AGPLv3, with the warpui_core and warpui UI crates dual-licensed MIT. OpenAI signed on as the founding sponsor of the repository, and the new contribution workflow funnels through Oz, Warp’s cloud agent orchestration platform. Warp’s blog post landed Tuesday morning and the Hacker News thread hit 220 points by the afternoon.

Warp founder Zach Lloyd was direct in the HN comments about the motivation: “Open-sourcing is fundamentally coming from our desire to build a successful business.” That’s a useful framing because it explains the structure of the release. The terminal is open. The runtime that ties Warp’s hosted AI features together is not.

What’s in the repo, what isn’t

The codebase is 98% Rust. macOS and Linux are supported, with a Windows port still on the roadmap. The 36,100 stars and 1,800 forks the repo carries on day one come from existing Warp users following the company’s main org rather than from a brand-new launch surge.

Two things are missing from the public history. First, the commit log starts fresh: contributors who want to branch off a pre-AI version of the codebase can’t, because Warp dropped the import without prior commits. The HN thread surfaced that complaint within hours. Second, the cloud platform is excluded by design. Warp’s block grouping and shared-workflow features all rely on Oz, and Oz stays proprietary along with the auth layer and any backend that talks to OpenAI’s models on the company’s behalf.

The license split is intentional. AGPLv3 on the body of the client means anyone who hosts a modified Warp behind a network service has to publish their changes back. MIT on the UI crates means a downstream maintainer can reuse Warp’s terminal-block widget without that same obligation. It’s the same open-core pattern Grafana and MinIO have used for years.

Open Agentic Development is the pitch

The framing Warp is leading with is a marketing label called Open Agentic Development. Stripped of the slogan, it means a contribution flow where Oz handles the planning, coding, testing, and pull-request opening, and human contributors mostly review and approve. Issues labeled ready-to-spec and ready-to-implement are the entry points; the agent picks them up, generates a plan, runs the tests, and posts a PR.

OpenAI’s engineering lead’s blurb on the launch reads, “Open source has long been central to how developers learn, build, and push the field forward. We’re excited to support experiments that explore how AI can help maintainers and contributors collaborate more effectively at scale.” Translated: GPT models drive Oz, and Oz drives Warp’s open-source repo. If the experiment works, Warp pitches Oz as the same agent stack for any other public project.

You can plug in another coding agent (Codex or Gemini CLI) to contribute instead, but the README is direct that Oz is the preferred path because the “skills and verification loops” are pre-tuned for the codebase. Reviews are still gated by Warp staff. This isn’t a community-led project pretending to be one, and the blog post doesn’t claim otherwise.

Who Warp is actually competing with

A top HN reply from user taupi cut to the answer: Warp’s competitors are “Claude Code, Codex, and Cursor, not Ghostty.” That tracks. People talking about Warp aren’t comparing it to iTerm2 anymore. They’re comparing it to whichever coding agent they’ve been paying $20 to $200 a month for.

The threat from below is that Anthropic’s Claude Code and OpenAI’s Workspace Agents both already run inside whatever terminal you’ve got. Warp’s bet is that owning the rendering layer plus the block model beats running as a CLI inside someone else’s terminal. The open-source move buys community momentum without giving up the part of the stack that makes it possible to charge.

The risk is the part Lloyd named on HN. Warp is selling Oz against well-funded rivals that can give the terminal away free as a loss leader. Open source is the marketing budget. If Oz doesn’t convert, the math doesn’t work.

What this means for you

If you already pay for Warp Pro, nothing changes today. Login is optional for anonymous use, tmux support is on the roadmap, and the AGPL client is now portable in a way the prior binary distribution was not. If you’ve been holding off because the client was closed, the license question is settled. Pin your fork if you want a known-AI-feature-free build.

If you maintain a project of any size and are watching the agentic-contribution model, this is the cleanest live test. Warp itself is the experiment. Watch the Oz-driven PR throughput on the repo over the next 90 days. If the volume holds and the review backlog doesn’t drown the maintainers, the model has legs. If not, it’s another governance lesson about how AGPLv3 plus a proprietary cloud product actually plays out in practice.