Important Feature Request: Shut down agent sessions especially when project is closed

[JnBrymn]

Today I opened up the tortie codebase as a project inside tortie. I had it open earlier and I had an agent session there, but then I closed the project. This time when I opened the project again, the agent session was still active. Nothing was running, but this terminal process has been open and holding substantial memory for a week.

I propose that sessions longer than some default (7 days?) be suspended AND sessions in projects that are closed be suspended when the project closes.

[gregce]

This is functioning as designed but I understand your q -- let me think about it.

In the meantime or maybe instead of what you're suggesting, I can add evict functionality for sessions in the session tab in diagnostics... if you've never seen this feature, give it a look

[JnBrymn]

It's cool to know that exists, but I need an easy way to kills stuff. I found out that I have a 22 day old Codex session that was started in the foo project (but I don't know the path). If I wanted to kill that process then then I'd have to locate foo, open foo, and manually kill the process. OR restart the computer.

Feels like something is needed here. I personally like the idea the closing a project stops all the sessions, and all sessions older than X days also get the axe. After all, it's pretty cheap to restart the sessions... so maybe I'd even say that sessions older than a day should be killed.