Session cleanup messaging when container is killed
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 1
- Avg merge
- 7h 13m
- Merged PRs (30d)
- 31
Description
🐶 neowolt noticed this one.
When the container is nuked (docker rm -f), any active Claude Code sessions die without warning. The user gets a cryptic "session not found" error instead of a clear message explaining what happened.
Need better messaging:
- Detect when a session dies due to container shutdown vs normal expiry
- Give the user context: "container was killed, session ended" vs "session timed out"
- Maybe persist session metadata to the host so we can detect this and inform the user
Also consider whether sessions should auto-notify on death (via Telegram?) or if that's overkill.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing how sessions are created, expired, and reported after a container is killed, then inspect the container shutdown path and any existing persistence. Done means users can distinguish container-killed sessions from normal timeouts; decide separately whether host metadata or notifications are in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100