Accidentally selected “This PC (Self-Hosted Worker)” and can’t continue or switch back

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I accidentally clicked “This PC” at the bottom of the chat while using the conversation and selected “This PC (Self-Hosted Worker)”. After that I can no longer continue the conversation, and I have no way to switch back to the previous state.

Steps to Reproduce

Clicked “This PC” at the bottom of the chat box and selected “This PC (Self-Hosted Worker)”.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.26.16 (user setup)
VS Code Extension API: 1.128.0
Commit: 8fcb8ace5c73fa31f2e2707fd6783160e4ed3e40
Date: 2026-10-21T09:02:57.211Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.11.16
Chromium: 148.0.7778.280
Node.js: 24.19.0
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.19044

Does this stop you from using Cursor

No - Cursor works, but with this issue

I don’t even know what this is — I’ve never used it. Could you please provide a toggle to hide it?

Hey @huanfei,

Sorry for the confusion. “This PC (Self-Hosted Worker)” moves the chat to a cloud agent that runs its commands through a worker process on your PC. Since that worker isn’t running on your machine, every message fails with “Your machine is offline”, and the option to move the chat back to This PC only appears once the worker has connected. That’s why the picker at the bottom has no dropdown right now.

The quickest way to keep working is to start a new chat in the same project with This PC selected. The old chat stays in the sidebar so you can still refer back to it.

If you want to get that original chat working again:

  1. Open Cursor Settings and find the Self-Hosted Workers section.
  2. Make sure “Enable local self-hosted workers” is on. If it already is, turn it off and back on.
  3. Fully quit Cursor and reopen it.
  4. Open the chat and click Retry on the banner.

Once the worker connects, the chat should continue, and clicking “This PC (Self-Hosted Worker)” should offer moving it back to This PC.

My “Enable local self-hosted workers” is now on, and I can’t turn if off.

And after trying again, my device is still offline.

Hey @huanfei,

You’re right, that switch can’t be turned off at the moment. On current versions the app keeps “Enable local self-hosted workers” on even after you switch it off, and that’s also why “This PC (Self-Hosted Worker)” shows up in the menu even though you never turned it on. This is a known issue we’re already tracking, and I’ve added your report to it. Please ignore my earlier step about making sure that setting is on.

You can keep working as normal: start a new chat in the same project with This PC selected. New chats run locally and aren’t affected. The chat that was moved can’t be switched back to This PC from the menu right now, so the new chat is the way forward. The old one stays in the sidebar if you want to copy anything from it. There’s no way to hide the option yet, so just keep choosing This PC.

The moved chat keeps saying your machine is offline because the background worker the app starts for it has never managed to connect from your PC. If you use a proxy or VPN app to reach Cursor, that’s likely the reason: the worker may not pick up the proxy Cursor uses, only one set in the HTTPS_PROXY environment variable. This is optional, since you don’t need the worker for normal use, but if you’d like to try:

  1. Open Windows Settings and search for “Edit environment variables for your account”.
  2. Add a new variable named HTTPS_PROXY whose value is your proxy address, for example http://127.0.0.1:7890 (use the port your proxy app shows).
  3. Fully quit Cursor and reopen it.
  4. Open the moved chat and click Retry.

Could you let me know whether you use a proxy or VPN app, and whether the chat connects after that? If it still says offline, the worker’s log files would help us see why. They should be in %APPDATA%\Cursor\User\globalStorage\anysphere.cursor-agent-worker (the files ending in .log); if that folder isn’t there, just let us know.

My worker had a problem because there was an issue with my git environment. After I fixed it, the worker started successfully, but I still can’t switch the conversation back. I think this is a BUG. Please fix it as soon as possible. It would be best to provide an entry point for hiding the switch button, because I never need this thing.