# Rush vs Warp Oz

Warp and Rush both start Claude Code or Codex in the cloud from an API. Warp comes from the terminal; Rush is only the API and what it returns.

Facts checked 17 October 2026. Prices and limits move. Read the citations.

**The short answer.** Pick Warp Oz when your team is in the Warp terminal and wants Warp Agent too. Pick Rush when you want runs that keep their machine, published limits and OpenCode as an option.

## The useful distinction

Warp Oz: Warp's cloud agent platform. It starts Warp Agent, Claude Code or Codex runs from a CLI, an API, Slack, Linear or GitHub Actions, in Docker-based sandboxes on Warp or your own compute.

The useful split is who builds the agent. Most products here run their own. Rush runs Claude Code, Codex or OpenCode, the vendors' own CLIs, and returns the result with the record of how it was made.

## Buyer questions

| Question | Rush | Warp Oz |
| --- | --- | --- |
| What runs | Claude Code, Codex or OpenCode, the vendors' own CLIs, or a saved agent built on one. | Warp Agent, Claude Code or Codex, picked per run. Claude Code and Codex call their provider directly. |
| Isolation | One E2B microVM per run with its own disk, memory, desktop and browser. It parks between turns and is removed on cancel or after 7 idle days. | An isolated sandbox per run from a Docker image environment, as a non-root user. Snapshots keep workspace changes for a later handoff. Setup over 30 minutes fails. |
| Result and pull request | A run on a repository works on its own branch and opens the pull request; a run whose checks fail ends needs_review, not completed. Reports and files come back as artifacts. | Pushes branches and opens pull requests on GitHub, authored by the Warp Factories GitHub App with team authorization. |
| MCP | Rush is an MCP server at api.prix.dev/mcp with 18 tools. A run also takes MCP servers by connection or inline. | MCP servers configured per environment for the tools a task needs. |
| Team | Everyone in the org sees the same Projects and runs, with who started each. Automations start runs from GitHub events, schedules, webhooks and Linear. | Slack mentions, Linear issue updates, GitHub Actions steps and schedules. SAML SSO on Business. SOC 2 and zero data retention with model providers. |
| Starting price | Free 5 agent-hours / month; Pro $20; Team $200 | Free with limited cloud agents; Build $20 / month with $20 of usage at API rates; Business $50 / user / month |
| Where it taps out | Three harnesses. Repositories through the GitHub App only. No self-host or customer VPC. A key runs 4 at once by default, up to 100. | Free has limited cloud agents. Self-hosted execution is Enterprise only. Build-plan concurrency is still being finalized. GitHub is the only documented forge. |

## When each side wins

### Rush wins when

- Each run keeps its own microVM with memory between turns, and parked time is free.
- Concurrency is published: 4 runs per key by default, up to 100.
- OpenCode is a third harness beside Claude Code and Codex.

### Warp Oz wins when

- Your team already uses the Warp terminal and its agent.
- You need self-hosted workers and data on Enterprise, with SOC 2 and zero data retention with model providers.
- You want native GitHub Actions and Linear triggers alongside Slack.

## Where Rush sits

Warp builds a sandbox from a Docker image per run and hands off through snapshots. A Rush session keeps the same microVM, disk and memory, across every follow-up until you cancel it or it sits idle for 7 days.

## Skip Rush if

- Rush runs three agents: Claude Code, Codex and OpenCode. It does not host an agent you wrote yourself.
- Repositories come through the Rush GitHub App. A GitLab or Bitbucket repository cannot be a run's repository yet.
- There is no self-hosted or customer-VPC deployment, and we do not publish a compliance report today.
- Compute is metered. Free includes 5 agent-hours a month and Pro 40, each with a weekly ceiling.
- You review the pull request. Rush does not merge for you.

## Questions people actually ask

### What is Warp Oz?

Oz is Warp's cloud agent platform, as titled on warp.dev/oz on 17 October 2026. Its docs call it the Automation Platform, and Warp Factories runs fleets of agents on it.

### Can I move from Warp Oz to Rush?

Yes. The steps, from Warp's own docs, are on the Migrate from Warp Oz to Rush page. Code you already pushed stays where it is.

### Does Rush need my own model account?

By default a run uses your own Claude or ChatGPT subscription or API key, and your provider bills the model calls. Rush meters the sandbox compute against your plan, and parked time is free.

## Keep reading

- [Warp Oz alternatives](https://getrush.ai/compare/warp-oz-alternatives.md)
- [Migrate from Warp Oz to Rush](https://getrush.ai/compare/migrate-from-warp-oz.md)
- [Warp Oz vs Cursor Cloud Agents](https://getrush.ai/compare/warp-oz-vs-cursor-cloud-agents.md)

## Sources

1. Rush, "Rush product requirements", retrieved 2026-09-15. https://getrush.ai/cloud
2. Rush, "Rush pricing (live contract on getrush.ai)", retrieved 2026-09-15. https://getrush.ai/pricing
3. Rush, "Isolation, plainly", retrieved 2026-10-17. https://getrush.ai/docs/concepts/isolation
4. Rush, "Results and proof", retrieved 2026-10-17. https://getrush.ai/docs/concepts/results-and-proof
5. Rush, "Usage and billing", retrieved 2026-10-17. https://getrush.ai/docs/concepts/usage-and-billing
6. Rush, "Rush MCP server", retrieved 2026-10-17. https://getrush.ai/docs/concepts/mcp-server
7. Rush, "Automations", retrieved 2026-10-17. https://getrush.ai/docs/concepts/automations
8. Warp, "Pricing", retrieved 2026-10-17. https://www.warp.dev/pricing
9. Warp, "Oz Cloud Agent Platform: Every agent at your command", retrieved 2026-10-17. https://www.warp.dev/oz
10. Warp, "Automation Platform (docs)", retrieved 2026-10-17. https://docs.warp.dev/_llms-txt/automation-platform.txt
11. Warp, "Warp Platform API 1.0.0 (OpenAPI)", retrieved 2026-10-17. https://docs.warp.dev/openapi.json