It keeps saying worker disconnected and please try again. Not letting me do any prompts.
Hey, thanks for the report. Based on the screenshot, this is a Remote Control My Machine error. The agent is running on a worker on your own computer, and Cursor lost connection to it while it was running. Since the chat is tied to that worker, the follow-up fails with Worker Disconnected.
What usually helps:
- Keep the computer that hosts the worker powered on and online with no sleep, keep Cursor open on the same project with Remote Control enabled, then just send a follow-up in the same chat. It will retry automatically.
- Don’t turn Remote Control off and on again. That unregisters the worker and can make it worse.
- If this specific chat keeps failing, start a new agent, cloud or local. Any edits from the crashed chats are still in your working tree on your machine, so nothing is lost.
We’re tracking this issue, but I can’t share an ETA yet.
To look into your case more closely, can you share:
- Your OS and Cursor version
- Whether the worker machine goes to sleep or loses network during runs
Related thread for context: Worker disconnected (under remote control)
Hey @ak_321 quick update on this thread. Since my last message, we shipped an improvement for this exact case: when the Remote Control (My Machine) chat loses connection to your computer, the follow-up now waits for the machine to come back online instead of failing right away with “Worker disconnected”. This is server-side, so you don’t need to update anything on your end.
Can you try again? Keep the computer running the agent powered on and online (no sleep), with Cursor open on the same project with Remote Control enabled, then send a follow-up in the same chat. Note: if the machine stays offline for more than an hour, the run will still fail, and that’s expected.
If it still fails, the details I asked for above would help:
- OS and Cursor version
- Whether the worker machine goes to sleep or loses network during runs
Let me know how it goes.
Fine, thanks it’s work for me, all chat (under remote) are back . have nice day