Migrate · Vercel · verified 17 Oct 2026
Migrate from Vercel Sandbox to Rush
Your repository and orchestration are yours. Moving to Rush replaces the clone, agent and push code with one request that returns the pull request.
Facts checked 17 October 2026. Prices and limits move. Read the citations.
Off-ramp
The steps
- 01
Find the code that creates a sandbox only to run a coding agent: create, clone, the agent command, push and your pull request call.
- 02
Commit the agent's instructions to CLAUDE.md or AGENTS.md so they load in every Rush run.
- 03
Keep Vercel Sandbox for code execution inside your own product, where Rush is not the fit.
- 04
Install the Rush GitHub App on the repository in Settings, Integrations, GitHub. A run that needs no repository needs no GitHub.
- 05
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.
- 06
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.
Rush
Where Rush sits
Leaving a Vercel Sandbox agent loop for Rush deletes the sandbox lifecycle and git code, and keeps your app on Vercel where it is.
Honest limits
Skip Rush if
- Vercel Sandbox 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.
FAQ
Questions people actually ask
What happens to my work on Vercel Sandbox when I leave?
Your repository and orchestration are yours. Moving to Rush replaces the clone, agent and push code with one request that returns the pull 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.
Cluster
Keep reading
Citations
Sources
Every factual claim on this page traces to one of these URLs. Retrieval date is 17 October 2026 unless the source prints an earlier published date.
- [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] Vercel, “Vercel Sandbox”, retrieved 2026-10-17. https://vercel.com/docs/sandbox
- [9] Vercel, “Vercel Sandbox pricing and quotas”, retrieved 2026-10-17. https://vercel.com/docs/sandbox/pricing
- [10] Vercel, “Run untrusted code with Vercel Sandbox, now generally available”, published 2026-01-30. https://vercel.com/blog/vercel-sandbox-is-now-generally-available
- [11] Vercel, “Vercel Sandbox vs E2B”, published 2026-03-20. https://vercel.com/kb/guide/vercel-sandbox-vs-e2b
- [12] Vercel, “Sandboxes (Vercel MCP tools)”, retrieved 2026-10-17. https://vercel.com/docs/agent-resources/vercel-mcp/tools/sandboxes
Next
Run the next Task on Rush
Connect a repository. Pick Claude Code, Codex, or OpenCode. Review the PR.