Compare · formerly Background Agents
Rush Cloud vs Cursor Cloud Agents
Same job on paper: isolated VM, unattended work, draft PR. Different engine. Cursor Cloud Agents are Cursor's Agent. Rush is the runtime for Claude Code, Codex, or OpenCode.
Facts checked 15 September 2026. Prices and limits move. Read the citations.
Stay on Cursor Cloud Agents if Cursor is already the team's editor. Move to Rush if the harness on the invoice is Claude Code, Codex, or OpenCode.
Proof
A real Rush Cloud run
Console capture of a coding Task that opened a pull request. Not a mockup.
Read this first
The useful distinction
Same job on paper: isolated VM, unattended work, draft PR. Different engine. Cursor Cloud Agents are Cursor's Agent. Rush is the runtime for Claude Code, Codex, or OpenCode.
Cursor's 2 September 2026 post says cloud agents create more than 60% of the pull requests Cursor merges internally. That number is Cursor using Cursor. It is not a bake-off against Claude Code.
Head to head
Buyer questions
| Question | Rush Cloud | Cursor Cloud Agents |
|---|---|---|
| Engine | Claude Code, Codex, OpenCode | Cursor Agent, curated models |
| Plan gate | Phoenix ID + connected repo | Paid Cursor plan |
| Approvals | Live steer, follow-up, exclusive lease | Auto-runs every terminal command |
| PR | One canonical PR + trajectory | Draft PR; signed commits |
| MCP in the cloud | Whatever the harness loads from the repo | HTTP and stdio. No SSE, no mcp-remote. |
| Dirty local files | Not in the product. Start from the remote. | Move to Cloud drops uncommitted files |
Decision
When each side wins
Rush Cloud wins when
- The team refuses to make Cursor the source of truth.
- The next Task might be OpenCode.
- A reviewer wants needs_review instead of a silent 'done'.
Cursor Cloud Agents win when
- The team already lives in Cursor and wants the same Agent off-laptop.
- You want computer-use artifacts and Cursor's environment snapshots.
- Slack @cursor and Linear automations are already the dispatch path.
When both
- Cursor's 2 September 2026 post says more than 60% of their internal PRs come from cloud agents. A team can keep that loop and still run Rush for harness-native work.
When neither
- Neither is a substitute for branch protection. Cursor docs state auto-run creates prompt-injection and exfiltration risk. Review the PR.
Rush Cloud
Where Rush sits
Rush starts from the harness binary and a prepared GitHub repo. Cursor Cloud Agents reconstruct a laptop environment in a Firecracker VM.
Sourced numbers
What we can chart
Cursor's own share of internal PRs from cloud agents
Vendor numbers from Cursor blogs. 24 Feb 2026: more than 30%. 2 Sep 2026: more than 60%. These are Cursor's internal merge share, not an independent win-rate.
Honest limits
Skip Rush if
- You need a team that already runs Claude Code, Codex, or OpenCode. Rush does not invent a fourth harness.
- Sandboxes are us-west-2. Customer VPC is roadmap. A signed compliance report is not something we publish today.
- Compute is metered. Sixty minutes are included per user per calendar month. The invoice bills sandbox time after that allowance.
- You will review the PR. Rush does not merge for you.
FAQ
Questions people actually ask
Can I use Rush and the vendor cloud side by side?
Yes. Many teams keep Claude Code on the web or Cursor Cloud Agents for a single-vendor loop and put Rush on the tasks that need a shared Project, a second harness, or a trajectory they can hand to a reviewer.
Does Rush replace Claude Code or Codex?
No. Rush runs those binaries. You keep the seat or the key. Rush is the runtime.
Where does the code go when I leave?
Anything pushed to your GitHub remote stays there. That is the off-ramp on every product in this set, including Rush.
Did Cursor publish an independent win-rate against Claude Code?
Not on the pages retrieved 15 September 2026. The 30% (Feb 2026) and 60% (Sep 2026) PR figures are Cursor's internal usage, reported by Cursor. CNBC reported roughly 35% on 24 February 2026.
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] Rush, “Rush Cloud product requirements”, retrieved 2026-09-15. https://tryrush.ai/cloud
- [2] Cursor Docs, “Cloud Agents”, retrieved 2026-09-15. https://cursor.com/docs/cloud-agent
- [3] Cursor Help, “Cloud Agents (help)”, retrieved 2026-09-15. https://cursor.com/help/ai-features/cloud-agents
- [4] Cursor Docs, “Cloud Agent security”, retrieved 2026-09-15. https://cursor.com/docs/cloud-agent/security
- [5] Cursor Docs, “Cloud Agent capabilities”, retrieved 2026-09-15. https://cursor.com/docs/cloud-agent/capabilities
- [6] Cursor, “Self-hosted machines for Cloud Agents”, published 2026-09-02. https://cursor.com/blog/self-hosted-machines
- [7] CNBC, “Cursor announces major update as AI coding agent battle heats up”, published 2026-02-24. https://www.cnbc.com/2026/02/24/cursor-announces-major-update-as-ai-coding-agent-battle-heats-up.html
Next
Run the next Task on Rush Cloud
Connect a repository. Pick Claude Code, Codex, or OpenCode. Review the PR.