Summary
Archiving already works as a lightweight “pause” for active sessions, but there is no configurable way to do this automatically after a session has been idle for a while.
When multiple sessions are left open, each one can keep a live runner process around. It would be helpful to let users choose an auto-archive timeout so finished sessions stop staying connected forever.
Expected behavior
Add a configurable auto-archive timeout in Settings, for example:
- Off
- 15 minutes
- 30 minutes
- 1 hour
- 2 hours
Once enabled, active sessions should be automatically archived after they have been idle for the selected duration.
Why this helps
- reduces long-lived idle sessions
- makes “archive = pause” more practical
- gives users control instead of requiring manual cleanup every time
Notes
A minimal implementation could be web-first:
- store the preference in local settings
- detect sessions that are still active but no longer thinking
- auto-call the existing archive action after the configured timeout
Summary
Archiving already works as a lightweight “pause” for active sessions, but there is no configurable way to do this automatically after a session has been idle for a while.
When multiple sessions are left open, each one can keep a live runner process around. It would be helpful to let users choose an auto-archive timeout so finished sessions stop staying connected forever.
Expected behavior
Add a configurable auto-archive timeout in Settings, for example:
Once enabled, active sessions should be automatically archived after they have been idle for the selected duration.
Why this helps
Notes
A minimal implementation could be web-first: