# Migrate from Tembo to Rush

The same harnesses, repositories and pull requests carry over. POST /v1/sessions with description, codeRepositoryIds and agent maps almost field for field onto a Rush session.

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

## Where Rush sits

Tembo to Rush is the shortest move on this site: POST /v1/sessions becomes POST /o/{org}/sessions, description becomes input, and Claude Code, Codex and OpenCode run on both.

## The steps

1. Map the call: Tembo's description is Rush's input, agent stays agent (claude, codex or opencode), and the repository moves from codeRepositoryIds to resources.
2. Use the same GitHub repositories. GitLab and Bitbucket repositories cannot move yet, because Rush reaches repositories through its GitHub App.
3. Replace polling with a webhook on the Rush key, and rebuild Linear, Slack or 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

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

The same harnesses, repositories and pull requests carry over. POST /v1/sessions with description, codeRepositoryIds and agent maps almost field for field onto a Rush session.

### 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 Tembo](https://getrush.ai/compare/rush-vs-tembo.md)
- [Tembo alternatives](https://getrush.ai/compare/tembo-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. Tembo, "Pricing – Tembo", retrieved 2026-10-17. https://www.tembo.io/pricing
9. Tembo, "Tembo", retrieved 2026-10-17. https://www.tembo.io/
10. Tembo, "Agents", retrieved 2026-10-17. https://docs.tembo.io/features/agents.md
11. Tembo, "Sandbox overview", retrieved 2026-10-17. https://docs.tembo.io/features/sandbox/overview.md
12. Tembo, "Tembo API overview", retrieved 2026-10-17. https://docs.tembo.io/api/index.md
13. Tembo, "Create a session", retrieved 2026-10-17. https://docs.tembo.io/api/v1/sessions/create-a-session.md
14. Tembo, "Tembo vs Devin", retrieved 2026-10-17. https://www.tembo.io/vs/devin