# In cursor IDE, agents stops working while Cursor Desktop app closes eventhough the agents run in remote machines **URL:** \ **Category:** Bug Reports\ **Tags:** ssh, chat\ **Created:** [November 13, 2026, 2:32am UTC](https://forum.cursor.com/t/in-cursor-ide-agents-stops-working-while-cursor-desktop-app-closes-eventhough-the-agents-run-in-remote-machines/178267 "2026-11-13T02:32:23Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Ranjith\_Poliyedath](https://avatars.discourse-cdn.com/v4/letter/r/ecc23a/32.png) [@Ranjith\_Poliyedath](https://forum.cursor.com/u/Ranjith_Poliyedath)\ **Post date:** [November 13, 2026, 2:32am UTC](https://forum.cursor.com/t/in-cursor-ide-agents-stops-working-while-cursor-desktop-app-closes-eventhough-the-agents-run-in-remote-machines/178267/1 "2026-11-13T02:32:23Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug In cursor IDE, agents stops working while Cursor Desktop app closes eventhough the agents run in remote machines . I use Cursor IDE in Mac. All my work is in remote machine connected via SSH. Ongoing work in agent chats gets interrupted/coses when I close the app. Ideally the work should continue because these should be running in remote machine. very frustrating to work on IDE. I only work with CLI now because of this. Codex and other harness handle this seemlessly. given a choice, users switch the harness for ease of use. ### Steps to Reproduce open cursor installed in Mac. connect to remote machine. open folder to any project workspace. start any agentic chat to do some work close the app. open the app again later to continue the work- but doesn’t work the agent get stopped. ### Operating System MacOS ### Version Information 3.27.12 ### For AI issues: which model did you use? any model available in cursor. same behavior ### Does this stop you from using Cursor Yes - Cursor is unusable ---
**Author:** ![Ranjith\_Poliyedath](https://avatars.discourse-cdn.com/v4/letter/r/ecc23a/32.png) [@Ranjith\_Poliyedath](https://forum.cursor.com/u/Ranjith_Poliyedath)\ **Post date:** [November 13, 2026, 2:38am UTC](https://forum.cursor.com/t/in-cursor-ide-agents-stops-working-while-cursor-desktop-app-closes-eventhough-the-agents-run-in-remote-machines/178267/4 "2026-11-13T02:38:27Z")
Version: 3.27.12 VS Code Extension API: 1.128.0 Commit: df132ffba90dfc15a12e6b8f020ba4e5d026c4b0 Date: 2026-10-23T02:27:47.076Z Layout: IDE 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: Darwin arm64 25.6.0 ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [November 13, 2026, 12:23pm UTC](https://forum.cursor.com/t/in-cursor-ide-agents-stops-working-while-cursor-desktop-app-closes-eventhough-the-agents-run-in-remote-machines/178267/8 "2026-11-13T12:23:15Z")
Hey @Ranjith_Poliyedath, this isn’t something wrong with your setup. Today a chat started in the editor is run by the desktop app, even on a Remote SSH workspace. The commands and edits happen on the remote machine, but the app drives the session, so quitting it stops the turn. Keeping agents working on the remote host after the app closes is a known gap that the team is aware of. There’s an earlier thread with the same ask here: [Durable agent runtime on Remote SSH/Cloud-workstations](https://forum.cursor.com/t/durable-agent-runtime-on-remote-ssh-cloud-workstations/159513) For now, the CLI in tmux on the remote machine is the reliable way to keep a long task going. In the desktop app, the Agents Window can pick an interrupted agent back up if you reopen within a couple of hours (Cursor Settings → General → Continue Interrupted Agents, on by default). That resumes the work when you come back, it doesn’t keep it running while the app is closed. Cloud Agents are another good way to keep agents alive even after your laptop is closed.