I with the newly created layout, sometime I see the option to move the agent to the cloud and also move it back to machine. Recently, with the new update, I’m not able to see the option. I only see the cloud option. It means that whenever I started it from the cloud, there is literally no option anywhere on either of the previous old editor and the new playground agent. Both of them do not show any kind of option, and I’m confused about how we can move it, switch it back and forth, if there’s an option. Recently, with a reporter issue, please feel free to help this one, because it is causing issues in my workflow.
In the last one or two updates, this was working fine, but I think the last one that came is what is not letting me move the agent back and forth.
Steps to Reproduce
You simply create a new agent, and then, once you are doing some basic conversation, you can then switch it into the cloud. Once you do it, you don’t next time see any option to move it back and forth. Even for new agents, right now I’m only seeing the option to move to the cloud, but there is no option to create it back to machine. Also, all of these agents were first created on the machine itself.
Expected Behavior
I’m expecting my agents to be able to move back and forth between machine and cloud.
Hey, in the Glass layout the option is called “Move to Local”, not “Move to Machine”, and it shows up as a pill in the agent UI. Important detail: the pill is intentionally hidden while the cloud agent is in CREATING or RUNNING status. It only appears after the agent finishes its current work.
Can you please check:
Is your cloud agent idle/completed, not actively running, at the moment you’re looking for the option?
If yes, send a screenshot of the agent panel and the Request ID from the chat, and we’ll take a look.
The migration flow between local and cloud is still being actively worked on, so there may be some rough edges with discoverability. If the agent is truly idle and the pill still doesn’t show up, that’s a bug, and we’ll need the details above to reproduce it.
Thanks for the extra info. In a cross-machine setup like yours where you started on a Mac Mini, then did Move to Cloud, then opened it on a MacBook, the Move to Local pill on the MacBook really won’t show up.
Reason: the MacBook doesn’t have the original local workspace or worktree where the agent started, so the UI can’t find a valid local destination and it won’t render the pill. This isn’t a bug in your session, it’s a current UX limitation. The team has a more general Move to picker on the radar, where you can choose a destination on any machine.
Workarounds:
Open the cloud agent on the Mac Mini. Move to Local will be there since the original local worktree exists on that machine.
I can’t share an ETA for the cross-machine flow yet, but I’ll post in the thread as soon as there’s an update. If the pill also doesn’t show on the Mac Mini when the agent is idle, send a screenshot and we’ll dig in.
I supposed it should work, considering both are my regular work machines that i used on and off for Cursor agents signed in to same account. But I get your point, but this do seem a bug idk.
Two other issues I noticed :
First if the cloud agents are only working for projects that are on Github , or can I sync local workspace as well if I can then I also see no option.
Secondly, I just opened a new github project not anywhere on mac mini, that is already on github.
Made simple commit and still no option of any thing to Move to Cloud/Machine.
Request ID : bc-70b54c18-88c3-4ecb-a259-8e79102f1c9b
This means, right now there is no option of any kind for any of the projects I have github, cloud synced, other machines or local to move either where.
