Oz

Oz is the orchestration platform that powers Warp's cloud coding agents. While Warp's terminal is the surface developers work in day-to-day, Oz is the underlying control plane that makes running coding agents at scale possible — whether one at a time or many in parallel across machines, repos, and teams.

The platform is built around four primitives: triggers, tasks, environments, and outputs. A trigger fires (a cron schedule, a Slack mention of @Oz, a Linear issue, a GitHub PR, a CI failure, a webhook, an API call, or a manual run), Warp's orchestrator creates a task and tracks its lifecycle, the agent executes on a host (optionally inside a Docker-based environment with repos and setup commands), and the run produces a persistent record — status, transcript, metadata, and outputs — that the team can audit and review.

Oz is multi-model out of the box. Agents can run on Claude (Sonnet 4.5, Opus 4.5), OpenAI GPT-5.2, Google Gemini 3 Pro, and other frontier models, and the platform supports industry-standard Skills (skill.md files) so existing agent definitions onboard quickly. It is also compatible with third-party CLI coding agents — Claude Code, Codex, Gemini CLI, and OpenCode — running inside Warp.

Three main interfaces are provided. The Oz web app at oz.warp.dev is for connecting a GitHub repo, picking a Skill, and launching an agent in a few clicks; it works on mobile too. The Oz CLI is the headless interface for CI runners, scripts, and remote machines, and reports progress back to Warp's servers for team observability. The Oz API and official Python and TypeScript SDKs let teams trigger agents from custom internal systems, build dashboards, and coordinate fanout, retries, and rate limiting at the application layer.

For execution, teams pick between Warp-hosted infrastructure (the default) or self-hosted execution on their own infrastructure (an Enterprise feature) where Oz still manages lifecycle and observability but code never leaves the customer's network. Secrets are stored at team or personal scope and injected at runtime so agents can call authenticated APIs without exposing values in logs.

First-party integrations with Slack, Linear, and GitHub Actions extract context (message text, PR diffs, CI logs) and create tasks automatically. Custom integrations let teams own the webhook and call the API or SDK directly. Centralized configuration — MCP servers, rules, saved prompts, environment variables, secrets — applies consistently across triggers, so the same workflow fires identically whether it's launched from Slack, CI, or a schedule.

Warp publishes usage stats from running its own product on Oz: 60%+ of merged PRs at Warp are created by Oz, with 20+ automations running daily and 6,700+ agents launched in a recent 30-day window. Oz is SOC 2 certified and offers Zero Data Retention with contracted LLM providers.