# Migrate from E2B to Rush

Nothing is locked in: the code is in your repository and the orchestration is yours. Moving to Rush turns that loop into one request.

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

## Where Rush sits

Moving an E2B agent loop to Rush keeps the isolation, because Rush runs on E2B microVMs, and deletes the code that installs the agent, clones the repository, pushes and opens the pull request.

## The steps

1. List what your E2B code does around the sandbox: the template, the keys it injects, the clone, the agent command, the diff it reads and the pull request it opens. Those are the steps a Rush run does for you.
2. Move the agent's instructions out of the code that builds the prompt and into CLAUDE.md or AGENTS.md in the repository, so every run loads them.
3. Keep E2B for work that is not an agent doing a task, such as a code interpreter inside your own product.
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

- E2B 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 E2B when I leave?

Nothing is locked in: the code is in your repository and the orchestration is yours. Moving to Rush turns that loop into one request.

### 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 E2B](https://getrush.ai/compare/rush-vs-e2b.md)
- [E2B alternatives](https://getrush.ai/compare/e2b-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. E2B, "E2B Pricing", retrieved 2026-10-17. https://e2b.dev/pricing
9. E2B, "E2B | The Enterprise AI Agent Cloud", retrieved 2026-10-17. https://e2b.dev/
10. E2B, "Sandbox persistence", retrieved 2026-10-17. https://docs.e2b.dev/sandbox/persistence
11. E2B, "Claude Code - E2B Docs", retrieved 2026-10-17. https://docs.e2b.dev/agents/claude-code
12. E2B, "Coding Agents - E2B Docs", retrieved 2026-10-17. https://docs.e2b.dev/use-cases/coding-agents
13. E2B, "Available servers - E2B Docs", retrieved 2026-10-17. https://docs.e2b.dev/mcp-gateway/available-servers
14. E2B, "e2b-dev/infra (GitHub README)", retrieved 2026-10-17. https://github.com/e2b-dev/infra