Migrate · Daytona · verified 17 Oct 2026

Migrate from Daytona to Rush

Your code is in your git remote and the loop around Daytona is yours. Moving to Rush replaces that loop with one request that returns the pull request.

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

Start a TaskAll comparison pages
Vendor sessionYour remoteBranches stayUninstall appNext Task
Moving work from Daytona to a Rush run

Off-ramp

The steps

  1. 01

    Find the Daytona calls that exist only to run a coding agent: create, clone, the agent command, commit, push and your pull request call.

  2. 02

    Commit the agent's instructions to CLAUDE.md or AGENTS.md so they load in every Rush run, instead of living in the code that builds the prompt.

  3. 03

    Keep Daytona for sandboxes that are not an agent doing a task, such as Windows or GPU workloads Rush does not run.

  4. 04

    Install the Rush GitHub App on the repository in Settings, Integrations, GitHub. A run that needs no repository needs no GitHub.

  5. 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.

  6. 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 Daytona for Rush is mostly deleting code: the sandbox lifecycle, the keep-alive around auto-stop, the clone and push calls and the pull request step become one Rush session.

Honest limits

Skip Rush if

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

Your code is in your git remote and the loop around Daytona is yours. Moving to Rush replaces that loop 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. [1] Rush, “Rush product requirements”, retrieved 2026-09-15. https://getrush.ai/cloud
  2. [2] Rush, “Rush pricing (live contract on getrush.ai)”, retrieved 2026-09-15. https://getrush.ai/pricing
  3. [3] Rush, “Isolation, plainly”, retrieved 2026-10-17. https://getrush.ai/docs/concepts/isolation
  4. [4] Rush, “Results and proof”, retrieved 2026-10-17. https://getrush.ai/docs/concepts/results-and-proof
  5. [5] Rush, “Usage and billing”, retrieved 2026-10-17. https://getrush.ai/docs/concepts/usage-and-billing
  6. [6] Rush, “Rush MCP server”, retrieved 2026-10-17. https://getrush.ai/docs/concepts/mcp-server
  7. [7] Rush, “Automations”, retrieved 2026-10-17. https://getrush.ai/docs/concepts/automations
  8. [8] Daytona, “Daytona - Secure Infrastructure for Running AI-Generated Code (pricing)”, retrieved 2026-10-17. https://www.daytona.io/pricing
  9. [9] Daytona, “Sandboxes | Daytona”, retrieved 2026-10-17. https://www.daytona.io/docs/en/sandboxes
  10. [10] Daytona, “Daytona MCP Server | Daytona”, retrieved 2026-10-17. https://www.daytona.io/docs/en/mcp
  11. [11] Daytona, “Git Operations | Daytona”, retrieved 2026-10-17. https://www.daytona.io/docs/en/git-operations
  12. [12] Daytona, “Bring Your Own Compute (BYOC) | Daytona”, retrieved 2026-10-17. https://www.daytona.io/docs/en/bring-your-own-compute
  13. [13] Daytona, “daytonaio/daytona (GitHub README)”, retrieved 2026-10-17. https://github.com/daytonaio/daytona

Next

Run the next Task on Rush

Connect a repository. Pick Claude Code, Codex, or OpenCode. Review the PR.

How the runtime works