Warp has launched Oz, a cloud-based orchestration platform for running, managing, and scaling coding agents. The platform targets teams that need to run parallel agents beyond local machine limits, automate recurring development tasks, and embed agent-driven workflows into custom apps.
Why Oz exists
Oz is designed around a few practical constraints encountered when using coding agents at scale: local CPU and git checkout limits, the operational burden of sandboxing and tracking agents, and the desire to build apps that incorporate agent intelligence. The platform emphasizes a terminal-first, programming-centric approach with first-class CLI, API, and Warp integration. Key design tenets include providing out-of-the-box scaffolding for teams, supporting arbitrary orchestration patterns, and offering both hosted and self-hosted deployment options.
Real-world uses at Warp
Three concrete internal examples illustrate Oz’s intent:
- Porting mermaid.js to Rust by parallelizing agents, launching one agent per diagram type and using the platform’s Computer Use capability to compare results with canonical outputs.
- Running a continually scheduled fraud detection agent that not only identified suspicious activity but also created PRs to block it; on one run it stopped nearly $60K of fraudulent usage.
- PowerFixer, a CLI triage app (source: https://github.com/warpdotdev/power-fixer-setup) that deduplicates new GitHub issues and dispatches agents to generate fixes, with session links for tracking progress.
These examples highlight Oz as both an interactive tool and a substrate for persistent automations.
Architecture and workflow
Oz is structured as an orchestration stack combining several elements:
- Auto-tracked agents that produce session links, audit trails, and artifacts (PRs, branches, plans).
- Cloud environments (Docker containers + git repos + startup commands) that provide agents with multi-repo context and are shared across teams. Environment setup typically takes minutes and can be done via the Warp slash command, the Oz web app, or the CLI/API/SDK. See the platform docs at https://docs.warp.dev/agent-platform/cloud-agents/environments.
- CLI, API, and SDK access for interactive control and programmatic launching.
- A built-in scheduler supporting cron-style recurring runs and programmatic triggers.
Launching examples include local runs like oz agent run --prompt "..." --share and cloud runs such as oz agent run-cloud --prompt "..." --environment <slug>. Any Skill placed in an environment (including those in a .agents/ directory or created for other coding agents) can be started as an agent with oz agent run-cloud --skill <slug> --environment <slug>. For developers building on top of Oz, the API and SDK provide the building blocks for apps like triagers, incident responders, and automated maintenance tools. Documentation and quickstart material are available at https://docs.warp.dev/agent-platform.
Pricing and availability
Oz is available to all Warp users on both free and paid plans. Agent consumption is billed via a combination of AI usage and compute usage, which together determine the credits an agent consumes when run on Warp’s hosting. For February, Build, Build Business, and Max users receive 1,000 bonus cloud agent credits (also granted to upgrades during the month). Bonus credits apply only to Warp-hosted cloud agents and expire after 30 days.
Where to read more
Full platform details, examples, and demos (including a YouTube playlist of Oz demos) are linked from the docs and Oz web app. Read the original announcement and technical write-up here: https://www.warp.dev/blog/oz-orchestration-platform-cloud-agents