When I reload the window or restart the Cursor app, all active terminal sessions are closed. This is particularly disruptive when the cursor application becomes unresponsive and requires a reload, as it terminates any running processes within those terminals (e.g., my running app development server)
Steps to Reproduce
Open an integrated terminal in Cursor.
Start a long-running process (e.g., npm run dev).
Execute the “Developer: Reload Window” command from the command palette.
Observe that the terminal is closed and the process has been killed upon reload.
Expected Behavior
Terminal sessions and their running processes should persist or be restored after a window reload or application restart, similar to the functionality in VS Code.
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
In VsCode the same command reloads all the windows but the terminal commands keep running.
For some reason for Cursor it closes ALL terminals.
This is pretty bad since I pretty often have extensions that cause force me to reload since they get in a bad state and I have to create the terminals again and start all the processes again.
Steps to Reproduce
Open terminal and write “ping google.com”.
Cmd+P and write “Reload window” and enter
on vscode the ping will continue working
on cursor there will be a new terminal
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Hello. Same here: since early September, reloading the windows now kills all running terminals (as well as ClaudCode extension’s dedicated terminal panel). Before September’25 it didn’t do that, terminals were preserved.
When Reloading Window, all the open terminals are closed and only one new appears. It stops everything that was running inside the terminals.
This didn’t happen a few weeks ago.
Steps to Reproduce
CMD+Shift+P > Developer: Reload Window
=> All the open terminals are closed and only one new appears. It stops everything that was running inside the terminals.
Expected Behavior
State is conserved between reloads as it was the case before.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
If the Cursor team had shared a timeline (not just “I hope it will be fixed”) over a month ago, you’d see fewer “same problem” replies. Coming from VS Code, this is a major workflow break. Our team (multiple freelancers on a client project) would like to move to Cursor, but our language extension forces several editor restarts a day. When Cursor kills terminals on reload/restart, it’s a huge disruption, unlike VS Code. In production debugging we have to redo port-forwarding, re-launch the app in debug mode, reconnect to the forwarded port, spin up k9s to inspect the cluster, navigate to the required pods again, etc. All of this is triggered by an extension error that a restart “fixes”, but Cursor wipes the terminals.
Can we get a concrete timeline when this will be fixed to be as it was again?
This is still an issue and not only does it clear the terminal session but wipes ALL terminals. Any expected fixes? It’s going to force us to move away from Cursor, really disruptive to our flow
This would be a killer feature. Perhaps the team could implement it using tmux or screen. Although it would probably have to be a VSCode fix and should probably be contributed upstream to VSCode.