Where does the bug appear (feature/product)? Background Agent (GitHub, Slack, Web, Linear) — specifically a Linear-spawned cloud agent, surfaced in the Cursor IDE Agents Window.
Describe the Bug Agents that originate in the cloud (spawned from Linear via @cursor) have no option to hand off to local. Right-clicking the agent in the Agents Window sidebar shows only Pin, Rename, Mark as Unread, Open in Web, Archive — there is no “Move to → Machine/Local/Desktop”.
Locally-started agents do show “Move to → Cloud” and can be moved to the cloud. So the handoff is asymmetric: local->cloud works, cloud->local is missing for cloud-origin sessions. The result is that there’s no way to continue a cloud-started session locally with its conversation context. The only workaround is to manually git fetch/checkout the agent’s branch and start a fresh local agent, which loses the entire chat history from the cloud session.
Steps to Reproduce
Spawn a cloud agent from Linear by mentioning @cursor on an issue (it creates a PR and reports back to Linear).
Open the Agents Window (Layout: glass). The cloud agent appears in the left sidebar.
Right-click the cloud agent.
Observe: only Pin / Rename / Mark as Unread / Open in Web / Archive — no “Move to → Machine/Local/Desktop”.
For comparison, right-click a locally-started agent → “Move to → Cloud” is present.
Expected Behavior Cloud-origin agents should offer a “Move to → Machine/Local/Desktop” (cloud->local) handoff that pulls the branch locally and transfers the conversation/session context, mirroring the documented local<->cloud handoff and the existing local->cloud direction.
Additional Information Reproduced on current stable (3.6.31) in the Agents Window, so this is not a layout issue (tested with both Layout: editor and Layout: glass). No changelog entry through the June 3, 2026 release addresses the cloud->local direction for cloud-origin agents. Appears related to existing reports that cloud-started agents show no move-to-machine option.
Does this stop you from using Cursor? No — Cursor works, but with this issue.
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Hey, thanks for the detailed report, this breakdown makes sense.
This is a known limitation, not a bug with your session. The Move to → Local option for a cloud agent only shows up when there’s already a local agent for the same repo in the Agents Window. The UI picks the local migration target from existing local agents that match the project, and the generic fallback of pulling to local from just a repo URL like the reverse flow local → cloud isn’t implemented yet. So if there’s no local agent for that repo, the whole Move to submenu stays hidden. The asymmetry you noticed is exactly because of this.
What you can do right now:
Open this repo locally and start a local agent in it. After that, the cloud agent should show Move to → Local.
Or keep working in the cloud session at https://cursor.com/agents. You can access it from any machine, and the chat context is preserved.
To be honest, cloud → local for cloud-origin sessions isn’t being actively built out right now, so I can’t give an ETA for a generic handoff. If anything changes, I’ll follow up.