# Migrate from Warp Oz to Rush

Branches and pull requests stay on GitHub. POST /agent/runs maps onto a Rush session; transcripts stay in Warp with no documented export.

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

## Where Rush sits

Moving from Warp Oz to Rush keeps the harness, Claude Code or Codex, and turns POST /agent/runs into POST /o/{org}/sessions with the same prompt.

## The steps

1. Confirm the branches and pull requests your runs opened are on GitHub; they stay there.
2. Turn the Docker environment's setup command into instructions in CLAUDE.md or AGENTS.md, so the agent installs what it needs in its Rush sandbox.
3. Replace POST /agent/runs with POST /o/{org}/sessions, and rebuild Slack, Linear and schedule triggers as Rush automations.
4. Install the Rush GitHub App on the repository in Settings, Integrations, GitHub. A run that needs no repository needs no GitHub.
5. Create an API key in the console under Developers, then start one run: POST /o/{org}/sessions with an agent (claude, codex or opencode) and the task as input. The same call is the create_session tool on the Rush MCP server.
6. Read the result: the pull request and its checks for code, or the report and files under artifacts. A run whose proof is missing ends needs_review, not completed.

## Skip Rush if

- Warp Oz still does the job you bought it for. This page is the off-ramp, not a reason to leave.
- 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 happens to my work on Warp Oz when I leave?

Branches and pull requests stay on GitHub. POST /agent/runs maps onto a Rush session; transcripts stay in Warp with no documented export.

### Do I rewrite my instructions for Rush?

Not if they live in the repository. Claude Code reads CLAUDE.md and Codex and OpenCode read AGENTS.md from the checkout, so a file you commit travels with every run. Settings held only inside another product's UI have to be copied into one of those files.

## Keep reading

- [Rush vs Warp Oz](https://getrush.ai/compare/rush-vs-warp-oz.md)
- [Warp Oz alternatives](https://getrush.ai/compare/warp-oz-alternatives.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