Warp is an agentic development environment, born out of the terminal, built for developers and teams who want a modern shell on Linux and macOS with AI coding agents working inside it.

What it is

Warp is a terminal that has grown into an agentic development environment. It is written in Rust, targets Linux and macOS, and supports the bash and zsh shells; its client codebase is open source and lives in this repository. It carries a built-in coding agent, and it also accepts external CLI agents such as Claude Code, Codex, and Gemini CLI. The project sits in the terminal and shell ecosystem, and its aim is to keep the shell as the place where development work happens rather than pushing it into a separate editor or chat window.

The concrete problem it addresses is the split between a plain terminal session and the agent tooling that now surrounds it. Instead of a conventional terminal emulator paired with separately installed and manually orchestrated CLI agents, Warp puts the agent surface and the shell in one environment. It extends that same idea to teams: Warp Factories are open infrastructure for building cloud software factories, defined in code, intended to deploy on any model or harness, with evals, benchmarks, and self-improvement built in. This repository is itself driven by Warp Factories, with agents triaging issues, writing specs, implementing changes, and reviewing pull requests.

Key capabilities

• A built-in coding agent, plus support for bringing an external CLI agent such as Claude Code, Codex, or Gemini CLI.
• Shell integration for bash and zsh on Linux and macOS, with a Rust codebase and a WebAssembly topic in the repository.
• The build.warp.dev dashboard, which shows Warp Factory agents triaging issues, writing specs, implementing changes, and reviewing PRs, along with top contributors and in-flight features.
• GitHub sign-in on that dashboard, so a contributor can track their own issues and click into active agent sessions in a web-compiled Warp terminal.
• Split licensing: the warpui_core and warpui crates carry the MIT license, while the rest of the repository is under AGPL v3.
• A contribution flow built around the ready-to-spec and ready-to-implement labels, issue templates, CONTRIBUTING.md, private security reporting, and the @oss-maintainers escalation handle.
• Local build scripts — ./script/bootstrap, ./script/run, and ./script/presubmit for formatting, clippy, and tests — documented alongside an engineering guide in AGENTS.md.

Who uses it and how

• Individual developers on Linux and macOS who want an agent inside the shell they already use with bash or zsh, instead of switching between a terminal and a separate agent client.
• Contributors who pick up issues labeled ready-to-spec or ready-to-implement, follow CONTRIBUTING.md, and coordinate with maintainers in the #oss-contributors Slack channel.
• Teams building their own cloud software factories on Warp Factories, which are defined in code and designed to run on any model or harness.
• Maintainers and observers who watch thousands of Warp Factory agents work through issues on build.warp.dev, or track progress on their own issues after signing in with GitHub.
• Engineers testing experimental behavior on the Preview build published at warp.dev/download-preview.

Getting started

Warp is installed by downloading it from warp.dev/download, with platform-specific instructions in the documentation at docs.warp.dev. To build from source instead, run ./script/bootstrap for platform-specific setup, then ./script/run to build and run Warp.

How it compares

No list of paid products that Warp replaces is provided in the facts, and no directly comparable terminal or agentic environment is named there either — the agents named in the README, such as Claude Code, Codex, and Gemini CLI, are integrations rather than substitutes. On the evidence available, Warp stands alone in this registry.

When to use it — and when not to

A self-hoster should note that this repository is the client codebase, that the agentic management workflows are powered by GPT models with OpenAI as founding sponsor, and that Warp Factories access is requested rather than freely available. Installation is download-based, and building from source depends on a platform-specific bootstrap script, so anyone expecting a package-manager install or a Docker image should plan around that. The project also carries a large open issue count at 5,218 and a licence split between MIT for the UI crates and AGPL v3 for everything else, which matters to teams that need uniform licensing; users who are not on Linux or macOS are out of scope.

./script/bootstrap   # platform-specific setup
./script/run         # build and run Warp
./script/presubmit   # fmt, clippy, and tests