# Migrate from Replit Agent to Rush

Push the Repl to GitHub with Replit's GitHub sync, then connect that repository to Rush. Hosting and the database stay on Replit unless you move them.

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

## Where Rush sits

Moving from Replit Agent to Rush starts with Replit's own GitHub sync: once the code is in a repository, Rush agents can work on it while Replit keeps hosting the app.

## The steps

1. Push the Repl to GitHub from Replit's Git pane, so the repository is the source of truth.
2. Write what the Replit Agent needed to know (how to run, test and seed the app) into AGENTS.md or CLAUDE.md.
3. Decide whether hosting and the database stay on Replit. Rush does not host apps; it opens pull requests against the repository.
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

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

Push the Repl to GitHub with Replit's GitHub sync, then connect that repository to Rush. Hosting and the database stay on Replit unless you move them.

### 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 Replit Agent](https://getrush.ai/compare/rush-vs-replit.md)
- [Replit Agent alternatives](https://getrush.ai/compare/replit-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. Replit, "Pricing", retrieved 2026-10-17. https://replit.com/pricing
9. Replit, "Starter Plan", retrieved 2026-10-17. https://docs.replit.com/billing/plans/starter-plan
10. Replit, "Replit Core", retrieved 2026-10-17. https://docs.replit.com/billing/plans/replit-core
11. Replit, "Replit AI Billing", retrieved 2026-10-17. https://docs.replit.com/billing/ai-billing
12. Replit, "Contribute to a GitHub project", retrieved 2026-10-17. https://docs.replit.com/use-cases/ship-github-change
13. Replit, "Version control", retrieved 2026-10-17. https://docs.replit.com/learn/projects-and-artifacts/version-control
14. Replit, "Connect via MCP", retrieved 2026-10-17. https://docs.replit.com/build/connect-via-mcp
15. Replit, "Replit MCP Server", retrieved 2026-10-17. https://docs.replit.com/platforms/mcp-server
16. Replit, "Publishing / deployments", retrieved 2026-10-17. https://docs.replit.com/learn/projects-and-artifacts/replit-deployments