Warp

Warp started as a better terminal and became something far more ambitious: an agentic development environment where the command line is the control surface for AI coding agents. The pivot is working, revenue is up 19x year-over-year, adding $1M in ARR every 10 days, driven almost entirely by the Oz cloud orchestration layer launched in February 2026. Oz lets developers dispatch up to 40 concurrent autonomous coding agents in the cloud, triggered by Slack messages, GitHub events, or cron schedules. The 75.8% SWE-bench Verified score (highest among terminal-based tools) is powered by frontier model access including Claude Opus 4.5 and GPT-5.2.

The terminal itself remains Warp's most distinctive UX decision. Block-based output groups every command and its response into a selectable, shareable, re-runnable unit, an experience that reviewers consistently call the killer feature even among users who never touch the AI. GPU-accelerated rendering keeps the interface snappy, and Warp AI suggests commands, explains errors, generates scripts, and debugs failures inline without leaving the terminal flow. For developers who live in the terminal, Warp makes a convincing case that you should not have to context-switch to an IDE for AI-assisted coding.

The pricing transition in 2026 introduced credit-based billing that has drawn mixed reactions. The free tier dropped from 150 to 75 monthly AI credits after two months, and meaningful agentic work requires the $18/month Build plan (1,500 credits, 20 concurrent cloud agents). Power users running heavy agent workloads need the $180/month Max tier.

BYOK (bring your own API key) support on Build and above lets teams use their own OpenAI, Anthropic, or Google credentials, which can significantly reduce effective cost. The main limitation is platform lock-in: Warp's terminal features are not transferable, and switching away means losing block-based output, AI integration, and cloud agent access simultaneously.