Cursor cloud runs

The Cursor Agent provider supports two run modes:

Mode	Where it runs
Local	On your machine. Standard agent run.
Cloud	On Cursor's cloud VMs. Survives Cerevisor restarts, laptop sleep, network drops.

Plan requirement: included on the trial, Pro and Founding membership. Not on Free.

When to use cloud mode

• Long-running workflows (multiple hours).
• Runs where Cerevisor might be closed before completion.
• Runs where laptop sleep would normally interrupt.

For most workflows, local mode is simpler, Cerevisor stays connected and you watch live progress. Cloud mode trades some immediacy for resilience.

Enabling cloud mode

Per workflow: Settings → Integrations → Cloud execution (Cursor only), then pick Cursor cloud instead of Local. The setting is saved with the workflow but only takes effect when the active provider is Cursor Agent.

Cloud-mode settings:

• Repository URL (required): the full git URL Cursor pulls onto its VM. This is distinct from your local project folder.
• Starting branch: which branch Cursor checks out (defaults to the repo's default branch).
• Work on current branch: commit directly to the starting branch instead of cutting a new one.
• Auto-create PR: automatically open a pull request for any code changes the agents made. Marked Destructive: Cerevisor asks you to confirm the first time a run starts with this enabled.
• Skip reviewer request: don't auto-request reviewers on PRs Cursor opens.

What happens when you click Run

1. Cerevisor asks Cursor to start the agent in the cloud, with your repository settings.
2. Cursor starts a VM and the agent begins work.
3. Cerevisor saves a record of the run on your computer before anything else happens, so the run can be found again even if Cerevisor closes or crashes.
4. Progress appears in the run window as it happens.

You can close the run window: the run continues on Cursor's VM. The Cloud Sessions button in the title bar lights up while a cloud run is active.

Surviving a Cerevisor restart

If you quit Cerevisor (or it crashes) during a cloud run:

1. The cloud VM keeps running.
2. The record of the run stays on your computer.
3. On next launch, Cerevisor looks for those records. A run that has been silent for more than a day is marked as failed.
4. The Cloud Sessions modal shows the runs you can reconnect to.

To reconnect:

• Click the Cloud Sessions icon in the title bar (only visible if any cloud runs exist).
• Find the run you want to reconnect to.
• Click Reconnect.

Cerevisor reconnects to the agent on Cursor's side, fetches its latest state, and shows you the run window again.

If the run finished while you were away, the window shows the final state and offers to fetch what it produced.

Artifacts

After every successful cloud run, Cerevisor downloads the files the run produced to ~/.cerevisor/cloud-artifacts/, in a folder for that run and agent.

You can fetch them again from the Cloud Sessions modal → Refetch artifacts.

Cancellation

To cancel an active cloud run:

• Cloud Sessions modal → find the run → Cancel.
• Cerevisor asks Cursor to cancel, and the cloud VM shuts down.

Dismissing finished runs

Completed runs stay in the Cloud Sessions modal until you dismiss them. Click Dismiss on a completed run to remove it from the list (its files stay on disk).

What doesn't work in cloud mode (v1)

• File intelligence: Cerevisor can't reliably track file changes that happen on Cursor's VM.
• MCP servers you added in Cerevisor: Cursor uses its own tool setup in the cloud.
• Per-tool permission prompts: what the agent may do is set before it starts, same as local Cursor and Codex.
• Loop & Enhance: each round starts a fresh cloud agent. It works, but less is carried over between rounds than in local mode.

Cost

Cursor bills cloud runs to your Cursor account. Cerevisor reports $0.00 in run cost, because Cursor does not report usage for these runs.

When NOT to use cloud mode

• Short workflows (under 5 minutes): starting a VM isn't worth the wait.
• Workflows that work heavily with files on your computer.
• Workflows where you want to approve actions one by one; that isn't available in cloud mode.

Why Cursor and not other providers

Cursor is the only provider Cerevisor supports that can run the whole agent in the cloud. With the other providers, the model may be hosted, but the agent's work is driven from your machine. In Cursor's cloud mode the entire agent runs on Cursor's infrastructure, including its tools and sandboxing.