I always use Cursor on remote SSH connections. I do not know if local projects have this same issue. And yes I use screen/tmux.
In a normal Cursor window, if I open a terminal, it stays open. The cursor window can be minimized for days while something is processing. It’s no problem at all. The terminal is still running and connected.
In Agents Window, even if I just switch to a different project for 30 minutes, if I switch back to the project I was in, the terminal I had is gone. Or at least hidden in a way that I can’t find it? So I have to open a new terminal in that project quite often. It’s not the end of the world. But it is a waste of time.
It seems like the Agents Window possibly doesn’t have whatever keep-alive that the normal (vs-code) Cursor window has?
Hey, thanks for the report. Good news: the terminal isn’t actually getting killed. The process and the tmux session keep running in the background. The issue is that in the Agents Window, the terminal panel doesn’t always rebind back to the right chat when you switch, so it looks like it’s gone.
Workaround until this is fixed: open the terminal list panel, the list icon at the top of the Terminal tab. You’ll see all terminals in the workspace, including ones started by other chats or agents under the other agents group. You can find your old terminal there instead of opening a new one.
This is a known bug in Glass restoration logic, and we’re tracking it, especially the case where after switching the panel comes back on the Browser tab. I can’t share an ETA for a fix yet. Let me know if the terminal list workaround helps.