zachlloyd
Joined 11 years ago
Joined 11 years ago
Note that we are going to add bring-your-own-model directly into Warp. Would love interested folks to weigh in on the discussion here: https://github.com/warpdotdev/warp/discussions/9619
You can still basically get back to the same way of working if you set new terminal sessions to be "agent sessions" and enable natural language detection. that's how i use it.
we have a lot of open source library dependencies and are grateful to the folks who worked on them
In terms of monetization, we actually don't monetize the terminal at all, we monetize our agent and our orchestration platform (www.oz.dev). Totally happy for you to use Claude or Codex CLI within Warp as your main driver.
We've added features to make using CLI coding agents easier (e.g. a file tree and code review) but they are all optional and customizable.
I outline the thought process in detail in our blog (https://www.warp.dev/blog/warp-is-now-open-source)
But the tl;dr is that I actually think we can build a better product, more quickly if we build it with our community + agents. I also think it's a unique product that I hope developers get a bunch of value from being able to customize and help improve. Our business is now mostly around agents and orchestration through Oz (https://oz.dev), so opening up the client and terminal felt natural.
The big thing for the "why now" though was the agent management piece.
Wrt the github stars, we had an issues-only repo prior and already had a significant number of stars before OSS today.
Founder @warp.dev (https://www.warp.dev), rebuilding the Terminal for the modern age. Prev: Principal Eng at Google Docs, Co-founder at SelfMade, Interim CTO at TIME.