This is a fully-local fork of Warp. It keeps Warp's terminal and agentic development environment, but removes the dependency on Warp's backend:
- No Warp API. The client never talks to Warp's servers for AI.
- No authentication. There is no login/account step — the app starts straight into a usable session.
- The agent loop runs locally. Instead of delegating the multi-agent loop to Warp's backend, this fork drives the loop on your machine and talks directly to an OpenAI-compatible API.
Because nothing is served by Warp, AI features only work once you configure a custom OpenAI-compatible endpoint. Point it at any compatible server — local (Ollama, LM Studio, vLLM, llama.cpp's server, …) or remote (OpenAI, OpenRouter, or any gateway that speaks the OpenAI API).
Configure it in Settings → AI → Custom inference / model providers: set the
base URL (e.g. http://localhost:11434/v1), an API key if your endpoint
requires one, and the model slug to use. Loopback and private-network hosts are
allowed (over plain HTTP for local hosts, HTTPS for public ones). Until an
endpoint is configured, the terminal works normally but agent/AI actions have
nowhere to go.
The build is driven by the scripts in script/. This fork builds as
the OSS channel, which needs no Warp-internal access.
Install the toolchain and build dependencies (Rust, protoc, GUI/runtime libs,
and the bundler):
./script/bootstrapThe
cargotoolchain installs under~/.cargo; make sure~/.cargo/binis on yourPATH(export PATH="$HOME/.cargo/bin:$PATH").
See WARP.md for the full engineering guide (coding style, testing, and platform notes).
Build and run straight from source with debug assertions. This is the fastest edit/run loop and what you want while hacking on the fork:
./script/runFor everyday use you want an optimized, packaged application you launch from your desktop — not a binary you start from another terminal. Build a release bundle of the OSS channel:
./script/bundle --channel ossLinux. To get a proper desktop entry (launcher icon, system integration) on
Debian/Ubuntu, build a .deb instead and install it system-wide:
./script/bundle --channel oss --packages deb --release-tag v0.1.0
sudo dpkg -i target/release-lto/bundle/linux/warp-terminal-oss_0.1.0_amd64.debAfter that, WarpOss appears in your application launcher like any other
installed app. (--packages also accepts rpm and arch.)
macOS. ./script/bundle --channel oss produces a .app bundle (and a
matching .dmg) at:
target/release-lto/bundle/osx/WarpOss.app
target/release-lto/bundle/osx/WarpOss.dmg
Copy the app into /Applications and launch it normally:
cp -R target/release-lto/bundle/osx/WarpOss.app /Applications/(Or open WarpOss.dmg and drag WarpOss into Applications.)
The rest of this README is inherited from upstream Warp.
Warp is an agentic development environment, born out of the terminal. Use Warp's built-in coding agent, or bring your own CLI agent (Claude Code, Codex, Gemini CLI, and others).
You can download Warp and read our docs for platform-specific instructions.
Explore build.warp.dev to:
- Watch thousands of Oz agents triage issues, write specs, implement changes, and review PRs
- View top contributors and in-flight features
- Track your own issues with GitHub sign-in
- Click into active agent sessions in a web-compiled Warp terminal
Maintaining a popular open-source project? Apply for Oz credits to explore Oz for OSS.
Oz for OSS is our partner program for bringing the same agentic open-source management workflows used in this repository to select partner repositories. We work directly with maintainers to implement workflows for issue triage, PR review, community management, and contributor coordination in a way that fits each project.
Warp's UI framework (the warpui_core and warpui crates) are licensed under the MIT license.
The rest of the code in this repository is licensed under the AGPL v3.
Warp's client codebase is open source and lives in this repository. We welcome community contributions and have designed a lightweight workflow to help new contributors get started. For the full contribution flow, read our CONTRIBUTING.md guide.
Tip
Chat with contributors and the Warp team in the #oss-contributors Slack channel — a good place for ad-hoc questions, design discussion, and pairing with maintainers. New here? Join the Warp Slack community first, then jump into #oss-contributors.
Before filing, search existing issues for your bug or feature request. If nothing exists, file an issue using our templates. Security vulnerabilities should be reported privately as described in CONTRIBUTING.md.
Once filed, a Warp maintainer reviews the issue and may apply a readiness label: ready-to-spec signals the design is open for contributors to spec out, and ready-to-implement signals the design is settled and code PRs are welcome. Anyone can pick up a labeled issue — mention @oss-maintainers on an issue if you'd like it considered for a readiness label.
To build and run Warp from source:
./script/bootstrap # platform-specific setup
./script/run # build and run Warp
./script/presubmit # fmt, clippy, and testsSee WARP.md for the full engineering guide, including coding style, testing, and platform-specific notes.
Interested in joining the team? See our open roles.
- See our docs for a comprehensive guide to Warp's features.
- Join our Slack Community to connect with other users and get help from the Warp team — contributors hang out in
#oss-contributors. - Try our Preview build to test the latest experimental features.
- Mention @oss-maintainers on any issue to escalate to the team — for example, if you encounter problems with the automated agents.
We ask everyone to be respectful and empathetic. Warp follows the Code of Conduct. To report violations, email warp-coc at warp.dev.
We'd like to call out a few of the open source dependencies that have helped Warp to get off the ground: