Sessions stuck permanently in "In use" state when not in use
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
Describe the bug
I have several sessions which were never marked no longer in use, and now do not show back up in the session list automatically. I have to /resume them every time, and accept a false warning that they're in use elsewhere. They've only ever been in use on one machine which shuts down regularly. This may be the cause of why the state was not cleaned up. However reopening these sessions does not reset the "In Use" flag, so the issue is permanent.
Affected version
GitHub Copilot CLI 1.0.84-6
Steps to reproduce the behavior
This is a guess
- Have a session
- Computer shuts down without cleanly terminating Agency
- Start agency, see session is still "In Use"
Expected behavior
Sessions should not be marked in use when they are not in use.
Additional context
No response
Contributor guide
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
Start by reproducing the reported shutdown scenario and inspect how the CLI records and reloads a session's "In Use" state. Verify whether reopening a stuck session changes that state, then confirm that sessions left by an unclean shutdown no longer remain hidden or trigger a false in-use warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100