Warp Open-Source

Love the move to open-source. For the agentic features, how are you balancing the 'magic' of automation with the developer's need for granular control? It's a tough line to walk.

Going open source is a bold move for Warp. The terminal space is one of those areas where developer trust matters more than features — and open source is the fastest way to earn it.As someone who spends most of my day in the terminal building and deploying, the "agentic" part is what interests me most. How does it handle context? The biggest limitation I've seen with AI-in-terminal tools is they lose context between commands. If Warp can maintain a running understanding of what I'm working on across a whole session, that's genuinely different from just having an inline copilot.

oss ftw!

Opening the source while keeping Oz as the heavy-lift layer is an interesting bet. Most OSS terminals stall because reviewers can't keep up with PRs, so routing implementation through managed agents and keeping humans on specs and verification might actually scale. I'm watching the local model question closely. For me, the dealbreaker is whether I can point Warp at a local Ollama endpoint without losing the agent orchestration UX. If Oz only orchestrates cloud models, that's a non-starter for anyone with NDA codebases. Any rough timeline on a BYO-endpoint config?

Super bold move, but also savvy. Proprietary software is no longer a moat like it once was; even more important is to consider that if you're not fixing your customer's edge cases and bugs at agentic speed, they're going to go elsewhere or just roll their own solution.Warp going open source means that the community can take more agency over their experience and fix the paper cuts that the Warp Corp team just doesn't have enough time or attention cycles to prioritize.I am curious about how fast PRs will be approved though, and what kind of scaffolding Warp will need to add to manage the community!Here's a high level look at the contribution flow. Steps owned by the contributor are shown in yellow; steps owned by the Warp team or Oz are shown in blue:

👋 Hey Product Hunt community,Zach here, founder of Warp. Two weeks ago we open-sourced Warp — and honestly, the response blew us away. We’re bringing it to Product Hunt today because this community is exactly the kind of community we want to build with.The short version: Warp 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. Community members shape direction and verify behavior. Oz-managed agents do a lot of the implementation heavy lifting. The Warp team reviews and ships.We're doing this because we think we can ship a better Warp, more quickly, by working with our community to supervise a fleet of agents. The biggest bottleneck to development is no longer writing code — it's the human-in-the-loop activities around it: deciding what to build, speccing it clearly, and making sure it's right. Opening up lets us be more responsive to users and work with them on the long tail of our backlog.The response so far has been pretty wild:25K+ new GitHub stars in week one — we more than doubled, to around 56K500+ unique contributors opened hundreds of PRsGreat conversations with the community about what people want to see in Warp nextWe still have a lot to figure out to build the right workbench for agentic development. For example, we’re actively discussing how to support local and arbitrary models in a way that matches what users actually want, not just what is easiest for us.Would love to hear: what would you want to build or fix in Warp? And what are you skeptical about?Check out the repo: https://github.com/warpdotdev/warpWatch what the agents are up to: https://build.warp.devThanks for checking it out — excited to build this together.— Zach