You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[question]: closing an agent tab does not kill the agent? #3293
When I create a new agent and then close it straight away, I can still see it on the list of Active conversations on the right bar. Is this the intended behaviour? I would expect the agent conversation to be killed or archived if I close the tab.
Context
Cursor 2 was closed right after opening it, but still showing on the list of Active sessions on the right bar.
Checklist
I've checked the README
I've searched existing issues for similar questions
Yes that I know. Just wanted to check if this is the desired behaviour and the rationale behind it. After only 2 days with Emdash I already have a ton of conversations listed there in the "Active" tab, even thou only 3 are actually active with an open tab.
I looked through current main. For PTY conversations, closing the tab releases the view attachment. The host's detachSession() deliberately does no work, so that path does not stop the agent process (source). The sidebar's Active group checks runtime session state, not open tabs (source). That matches what you're seeing.
It explains the implementation, but I can't speak for the intended UX. Your distinction still makes sense: "tab is open" and "agent is running" are separate states. A short explanation of those states in the UI or docs would help.
Activity
jschwxrz commentedon Oct 4, 2026
Hi, you can right click on the conversation in the sidebar to see an option to kill the session
igoramadas commentedon Oct 4, 2026
Yes that I know. Just wanted to check if this is the desired behaviour and the rationale behind it. After only 2 days with Emdash I already have a ton of conversations listed there in the "Active" tab, even thou only 3 are actually active with an open tab.
Eigenwise commentedon Oct 5, 2026
I looked through current main. For PTY conversations, closing the tab releases the view attachment. The host's
detachSession()deliberately does no work, so that path does not stop the agent process (source). The sidebar'sActivegroup checks runtime session state, not open tabs (source). That matches what you're seeing.It explains the implementation, but I can't speak for the intended UX. Your distinction still makes sense: "tab is open" and "agent is running" are separate states. A short explanation of those states in the UI or docs would help.