Migrate · Google · verified 15 Sep 2026

Migrate from Google Jules to Rush

Pushed PRs stay on GitHub. Tasks can be deleted. No documented portable export of Jules session history.

Facts checked 15 September 2026. Prices and limits move. Read the citations.

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

Off-ramp

The steps

  1. 01

    Pushed pull requests stay on GitHub. Jules documents no export of session history; delete tasks you no longer need.

  2. 02

    Replace the jules issue label with a Rush automation on issues.labeled, or call the API from your own workflow.

  3. 03

    Uninstall the Jules GitHub App once Rush runs on the repository.

  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

Jules to Rush keeps the GitHub repository and the issue as the task; the jules label becomes a Rush automation on issues.labeled.

Honest limits

Skip Rush if

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

Pushed PRs stay on GitHub. Tasks can be deleted. No documented portable export of Jules session history.

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 15 September 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] Google, “Jules - An Autonomous Coding Agent”, retrieved 2026-09-15. https://jules.google/
  9. [9] Google, “Limits and Plans | Jules”, retrieved 2026-09-15. https://jules.google/docs/usage-limits/
  10. [10] Google, “FAQ | Jules”, retrieved 2026-09-15. https://jules.google/docs/faq/
  11. [11] Google, “Environment setup | Jules”, retrieved 2026-09-15. https://jules.google/docs/environment/

Next

Run the next Task on Rush

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

How the runtime works