# Cannot re-enable Remote Control after switching session to "This PC" **URL:** \ **Category:** Bug Reports\ **Tags:** agents-window, remote-control\ **Created:** [July 24, 2026, 11:37am UTC](https://forum.cursor.com/t/cannot-re-enable-remote-control-after-switching-session-to-this-pc/166559 "2026-07-24T11:37:08Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Maciej\_Wachnik](https://avatars.discourse-cdn.com/v4/letter/m/a183cd/32.png) [@Maciej\_Wachnik](https://forum.cursor.com/u/Maciej_Wachnik)\ **Post date:** [July 24, 2026, 11:37am UTC](https://forum.cursor.com/t/cannot-re-enable-remote-control-after-switching-session-to-this-pc/166559/1 "2026-07-24T11:37:08Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug After enabling Remote Control in Agents Window → Settings → Agents (also “Keep this computer awake”), I ran a session in Remote Control mode. I then switched the session to This PC. Afterwards I cannot restore Remote Control for the same chat: Continue on shows only This PC (no Remote Control option) Typing /rem in agent input only suggests remove-plugin, not /remote-control Global Remote Control setting remains ON OS: Windows. Workspace is git-backed with remote. Feature worked earlier on this same thread until switched to This PC. ### Steps to Reproduce Expected: ability to switch the same agent session back to Remote Control (via Continue on and/or /remote-control). ### Operating System Windows 10/11 ### Version Information Version: 3.12.29 (user setup) VS Code Extension API: 1.128.0 Commit: cd1c87ff9b66021918fb9731605f8d1d5fd2f0b0 Date: 2026-07-21T03:26:05.811Z Layout: Agent Window Build Type: Stable Release Track: Default Electron: 40.10.3 Chromium: 144.0.7559.236 Node.js: 24.15.0 V8: 14.4.258.32-electron.0 xterm.js: 6.1.0-beta.256 OS: Windows\_NT x64 10.0.26200 ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [July 24, 2026, 12:16pm UTC](https://forum.cursor.com/t/cannot-re-enable-remote-control-after-switching-session-to-this-pc/166559/5 "2026-07-24T12:16:53Z")
Hey, thanks for the detailed report with the version and steps, that helped. This is a bug on our side. After switching a chat to This PC, it still stays classified as a cloud or RC agent, so Continue on only offers This PC, and `/remote-control` doesn’t show up even though the global toggle is on. I’ve reported it internally, but I can’t share an ETA for a fix yet. For now, a couple workarounds: - Remote Control itself isn’t broken, new RC sessions start fine. Launch a fresh agent via Run on → This PC (Remote Control). - For the stuck chat, Reload Window via `Cmd+Shift+P` or `Ctrl+Shift+P` then run Reload Window, then reopen the local This PC chat thread from the sidebar. Once it’s correctly local again, the chat should offer `/remote-control`. If RC still doesn’t come back after that, let me know and we’ll dig in further. ---
**Author:** ![Maciej\_Wachnik](https://avatars.discourse-cdn.com/v4/letter/m/a183cd/32.png) [@Maciej\_Wachnik](https://forum.cursor.com/u/Maciej_Wachnik)\ **Post date:** [July 24, 2026, 12:55pm UTC](https://forum.cursor.com/t/cannot-re-enable-remote-control-after-switching-session-to-this-pc/166559/6 "2026-07-24T12:55:03Z")
> [@deanrie](#): > > ching a chat to This PC, it still stays classified as a cloud or RC agent, so Continue on only offers This PC, and `/remote-control` doesn’t show up even though the global toggle is o Hi, thanks for looking into this and for the workarounds. A few clarifications from my side: **On classification after switching to This PC** After I switch the chat to **This PC** , it no longer behaves like a Cloud / Remote Control session for me. Specifically, I lose access to that chat from my phone (Android, via browser). That suggests the session type does change to local at least from a mobile/access perspective. So from my end it doesn’t look like it simply “stays classified as cloud/RC” — more like it becomes local, but then `/remote-control` still never becomes available again on that same thread. `Continue on` only shows **This PC** , and `/remote-control` doesn’t appear even though the global Remote Control toggle is on. **New RC sessions** Confirmed — Remote Control itself works. Starting a fresh agent with **Run on → This PC (Remote Control)** works as expected. **Reload Window workaround** I tried **Ctrl+Shift+P → Reload Window** , then reopened the local **This PC** chat from the sidebar. `/remote-control` still does not appear for that stuck chat. ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [July 24, 2026, 1:12pm UTC](https://forum.cursor.com/t/cannot-re-enable-remote-control-after-switching-session-to-this-pc/166559/7 "2026-07-24T13:12:58Z")
Thanks for checking and adding the phone detail, that really helps. The fact that mobile access drops confirms the chat is actually becoming local. But during migration it keeps a link to the old cloud session, and that’s why `/remote-control` and Remote Control in Continue on don’t come back for this specific thread. That’s also why Reload Window doesn’t help here, the thread state is already locked in. Honestly, there isn’t a reliable way to restore Remote Control on this stuck chat right now. For now the workable path is to continue the task with a fresh agent via Run on \> This PC (Remote Control), like you confirmed. I’ve reported the bug internally with your details. I can’t share an ETA yet, but I’ll post an update in the thread as soon as I have one. ---
**Author:** ![Maciej\_Wachnik](https://avatars.discourse-cdn.com/v4/letter/m/a183cd/32.png) [@Maciej\_Wachnik](https://forum.cursor.com/u/Maciej_Wachnik)\ **Post date:** [July 24, 2026, 1:49pm UTC](https://forum.cursor.com/t/cannot-re-enable-remote-control-after-switching-session-to-this-pc/166559/9 "2026-07-24T13:49:04Z")
Thanks for the explanation and for reporting the issue. ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [September 21, 2026, 12:53pm UTC](https://forum.cursor.com/t/cannot-re-enable-remote-control-after-switching-session-to-this-pc/166559/11 "2026-09-21T12:53:01Z")
Hey @Maciej_Wachnik, circling back to this thread. Over the last few months, we’ve made a bunch of improvements to how agents switch between Remote Control and This PC, including the Continue on picker and the `/remote-control` command. Since you posted, the version has moved forward a lot (current stable is 3.21.x). If you still can’t switch the chat back to Remote Control after moving it to This PC on the latest version, please start a new thread with updated details (version, steps), and I’ll take a look. I’m going to close this one for now.