-
Notifications
You must be signed in to change notification settings - Fork 5k
Warp is now open source #9240
-
Today we're announcing a change in how we build Warp: the client is now open source, and we invite the community to participate in building it using an agent-first workflow managed by Oz, our cloud agent orchestration platform. Full write-up on the blog: https://www.warp.dev/blog/warp-is-now-open-source.
The short version: we think the future of agentic development is wide open, and we want to figure out what the right workbench for building with agents looks like with the community rather than keep guessing at it privately. Oz does most of the implementation heavy lifting on approved issues. The community shapes direction and helps verify. The Warp team reviews and ships. You can take a look at the contribution flow in our CONTRIBUTING.md.
We want this discussion to be a home base for the big-picture conversation — what you think of the direction, what you'd want to build on top of Warp, what you're skeptical about. Bugs and feature requests belong in Issues, but for the meta stuff, this is the place. Thanks for being here — excited to build this together.
— Zach
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 75 -
😄 10 -
🎉 46 -
😕 1 -
❤️ 25 -
🚀 24 -
👀 1
Replies: 11 comments 10 replies
-
So, no more login to open the terminal ?
Beta Was this translation helpful? Give feedback.
All reactions
-
i logged in using a burner email
Beta Was this translation helpful? Give feedback.
All reactions
-
That still means requests being sent to a centralized backend and individually tracking you even if you wouldn't be identifiable.
Beta Was this translation helpful? Give feedback.
All reactions
-
how is that detrimental to me
Beta Was this translation helpful? Give feedback.
All reactions
-
😕 1
-
login requirement was lifted back on Nov 2024. https://www.warp.dev/blog/lifting-login-requirement
Beta Was this translation helpful? Give feedback.
All reactions
-
Not for BYOK and BYOLLM.
Beta Was this translation helpful? Give feedback.
All reactions
-
This feels like the right strategic move at the right time. With today's AI/vibe-coding capability, the advantage of a closed-source product with a similar UX can erode very quickly: people can now prototype, fork, and iterate on missing pieces much faster than before.
In that environment, the durable moat is less about keeping the client private and more about trust, review quality, product taste, extension surface, and the speed at which the community and maintainers can turn good ideas into shipped improvements.
Open-sourcing the client makes Warp much more credible as the workbench for agentic development. Excited to see how the contribution flow around Oz works in practice.
Beta Was this translation helpful? Give feedback.
All reactions
-
This is fantastic news! Maybe now we can get local models to integrate!
Beta Was this translation helpful? Give feedback.
All reactions
-
🚀 Congrats to the team and fair winds to Warp! It's a rare case when a product of this scale - a million active developers, five years of work - doesn't lock its work behind closed doors but instead entrusts it to the community.
For me personally, this isn't just a chance to "use a tool" - it's a chance to actually shape what a developer's workspace looks like in the age of agents. Truly grateful for the opportunity to take part.
To fellow community members: don't sit this one out. The future of agentic IDEs is literally being written in the open right now - and it will be exactly what we make of it. If everyone contributes even a small issue, a bug report, a patch, or an idea on the roadmap, we'll end up with a tool built around real-world needs, not someone's vision in a vacuum. Moments like this don't come often; it would be a shame to let it slip.
Good luck, Warp! 🚀
Beta Was this translation helpful? Give feedback.
All reactions
-
Can we bring our own AI model and skip login?
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
Would love to see open sourcing your full warp_proto_apis.
The Warp client does NOT directly call any LLM provider APIs. All AI requests flow through Warp's own backend at app.warp.dev via GraphQL. The client is an intelligent terminal with a beautiful UI, but the AI brain — LLM routing, model selection, billing, streaming orchestration, conversation state — lives entirely on Warp's servers. BYOK (Bring Your Own Key) keys are collected from users but forwarded to Warp's server, which then calls provider APIs on behalf of the user.
Pointing Warp at a custom OpenAI-compatible API (e.g., self-hosted vLLM) is difficult. The recommended approach is a Warp Backend Proxy that intercepts and translates GraphQL operations between the client and your endpoint — zero client modifications needed.
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 4
-
Help docs already mention Fireworks as an AI provider.
I just want BYOK with Fireworks
Beta Was this translation helpful? Give feedback.
All reactions
-
@zachlloyd Hi Warp team, can you upload the redistribution archives for all OS in the GitHub release page?
I have tried several times to download the Warp from your official website(warp.dev) or from winget under windows, all failed due to the transfer is terminated in the middle way.
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 2
-
+1
Beta Was this translation helpful? Give feedback.
All reactions
-
I tried over 20 times to download the installer for Windows, only one was successfully.
The later upgrade from Winget or direct download failed, tried many times. @zachlloyd
Beta Was this translation helpful? Give feedback.
All reactions
-
Personally I didn't have a download issue, but having to do multiple clicks and cancel a download in order to get a link I can (削除) wget (削除ここまで)aria2c because the link isn't a .deb link is very infuriating. GitHub releases are plain and simple. Having to go to the official website rather than the source code repository even for binaries isn't right for an open source projet. @advait-m @alokedesai @danielpeng2 @dannyneira @ianhodge @kevinyang372 @szgupta
Beta Was this translation helpful? Give feedback.
All reactions
-
Quick update on one of the big themes in this thread: Zach shared our plan for BYOK, arbitrary OpenAI-compatible endpoints, local models, and ACP support. Near term, BYOK is planned for the free plan and arbitrary OAI-compatible endpoints; longer term, we’re working toward client-side local model support and ACP so users can bring their own inference without routing through Warp’s servers. Details: #9619 (comment)
Beta Was this translation helpful? Give feedback.
All reactions
-
Enable full support for bringing your own llm apis, it's basically open source, but not open source at the same time with the core being gated still.
Beta Was this translation helpful? Give feedback.
All reactions
-
Without being able to modify the models URL and use whatever model provider you want / local it seems like a obvious win for everyone. Enterprises often use custom URL's. It is very common across the board so adding it would help paying and open source users!
Very weird its not in
Beta Was this translation helpful? Give feedback.
All reactions
-
Buying some ads with this move? The software still requires login.
Beta Was this translation helpful? Give feedback.
All reactions
-
Quick update on one of the themes in this thread: we’ve shipped BYOK on the Free plan for individual users, and Warp now supports custom inference endpoints compatible with the OpenAI Chat Completions API.
That means you can use your own OpenAI, Anthropic, or Google API key, or connect Warp to an OpenAI-compatible endpoint such as OpenRouter, LiteLLM, z.ai, an internal gateway, or a hosted/self-hosted inference setup.
Docs:
- BYOK: https://docs.warp.dev/agent-platform/inference/bring-your-own-api-key/
- Custom inference endpoints: https://docs.warp.dev/agent-platform/inference/custom-inference-endpoint/
Fully client-side local model support and external harness support are still separate directions. We’re planning a lightweight local client harness for direct local model connections, and support for Agent Client Protocol so developers can bring other harnesses into Warp’s terminal UI.
If you try the new inference setup and hit a specific issue, please open a focused GitHub issue with the provider, endpoint, model, and error so we can track it directly.
Beta Was this translation helpful? Give feedback.
All reactions
-
🚀 2