This page is labeled Warp Code, but the official Warp materials checked on April 16, 2026 present it as the code-focused layer inside a broader product rather than as a separate standalone editor. Warp now describes itself as an Agentic Development Environment. The homepage splits the product into Warp Terminal, which it calls a modern terminal for agentic coding, and Oz, which it calls the orchestration platform for cloud agents. That framing matters because the old English page undersells what users are actually being asked to evaluate.
The official agent documentation makes this broader workflow concrete. Warp says Oz powers interactive local agents for real-time coding assistance inside the app, but it also powers autonomous cloud agents that can run from triggers, schedules, and integrations. The same docs emphasize tracking, auditing, and sharing runs, plus starting them from the web app, CLI, or API. That means Warp is trying to cover both the moment when you are typing in front of the terminal and the background automation layer that continues when you are not.
The pricing page is equally important because Warp’s real fit now depends heavily on how much AI usage and codebase scale you need. On April 16, 2026, Warp listed the Free plan at $0 per month with limited AI credits and model access, limited cloud agents access, and limited codebase indexing. The AI features table showed 150 monthly credits for the first two months and 75 per month after that, alongside 4 concurrent cloud agents, 3 indexed codebases, 3,000 files per codebase, and 30 cloud conversations. This is enough to make Warp worth testing, but it also means larger codebase or higher-volume automation users should not assume the free tier tells the whole story.
The same pricing page shows where Warp becomes meaningfully stronger. Warp listed Build as starting at $18 per month with 1,500 credits per month, access to frontier OpenAI, Anthropic, and Google models, extended cloud agents access, highest codebase indexing limits, and unlimited Warp Drive objects and collaboration. Business started at $45 per user per month and added automatically enforced team-wide zero data retention plus SAML-based SSO. Our grounded judgment is that this plan structure makes Warp easier to recommend to codebase-heavy users and teams than to casual users who only want a small amount of local AI assistance.
The built-in code editor is one of the most useful corrections to make on this page. Warp does have a native editor, but the official docs are careful about what it is for. Warp says the editor is designed for quick, in-flow edits alongside agent conversations and includes syntax highlighting, tabs, find and replace, Vim keybindings, a file tree, and LSP support for several major languages. That is real functionality, but it is not the same thing as promising a full IDE replacement. The product story is closer to “stay in the workflow and land changes faster” than to “replace your main editor for every case.”
Warp’s Code Review panel is another feature the old English page misses. The docs show the panel opening from the Git diff chip, from an agent conversation review button, or from Warp’s top bar. Warp says it can show uncommitted changes, compare against main or master, update in real time as files change, attach diffs as agent context, edit diffs directly, and revert changes. This is important because it gives Warp a real diff-and-review workflow instead of leaving users with only chat output and blind apply buttons.
The permissions system is one of Warp’s stronger trust signals. The official documentation says users can configure how much autonomy the coding agent has when applying diffs, reading files, creating plans, and executing commands. Warp documents three levels: Agent Decides, Always ask, and Always allow. It also warns that fully allowing diff permissions gives the coding agent full autonomy. For a page like this, that means the right recommendation is not simply “Warp is powerful,” but “Warp is powerful and lets you tune how much control you hand over.”
The installation guide is also much more practical than the current thin page. Warp says all installation options support auto-update, and the docs list support for macOS, Windows x86_64 and ARM64, and Linux x86_64 and ARM64. On Windows, Warp requires version 1809 or later and documents both the installer path and WinGet. The same setup guide says login is optional, that Warp can be used offline after the first launch, and that supported shells include bash, fish, zsh, and PowerShell (pwsh). That gives readers a much firmer install baseline than generic copy does.
For Windows users specifically, Warp’s launch blog is still useful grounding material. Warp says Windows support includes PowerShell, WSL, and Git Bash, with both x64 and ARM64 builds. The blog also says the core experience is nearly identical to macOS and Linux, that the app is written in Rust and rendered directly on the GPU, and that login is optional even if some AI and collaboration features are limited when logged out. For an aidown reader on Windows, that is much better decision material than a generic marketing paragraph.
The Oz web app closes the loop on why Warp can feel larger than a terminal. Warp says the web app can monitor runs, start quick runs, manage schedules, configure environments, and set up integrations, and it works from a browser or mobile device. That means users who adopt cloud agents are not limited to the local desktop window. They get a lightweight operations surface around their automations as well. This is one of the clearest reasons to recommend Warp to developers and teams who see value in recurring or background agent work.
Our grounded judgment is that Warp Code is worth installing for developers who want terminal work, agent conversations, quick code edits, diff review, and optional cloud automation to stay close together. It is a weaker fit for users who mainly want a tiny standalone autocomplete helper, who expect the free tier to cover large long-running codebase workflows, or who prefer living entirely inside a traditional full IDE with little interest in terminal-first work. The right recommendation is not that Warp replaces every developer tool. It is that Warp offers one of the clearer terminal-centered agent workflows right now, with practical review and permission controls that make that workflow easier to trust.
