Session in running state, but model has returned an answer
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Short summary
Session appears to keep running indefinitely even though response is fully returned.
Affected version or release
v1.1.16
Installation context
MacOS Tahoe 26.6.2
What happened?
Sessions appear to keep running, though response is returned. Happening across multiple sessions. Tried app update and restart with no luck.
This also means that when I manually "stop" the session, queued messages are lost.
Steps to reproduce
- Start a session
- See response returned, yet session appears to keep running.
Expected behavior
Session should enter the "response returned" state.
Additional context
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
No files, tests, or entry points are named. First reproduce the issue on macOS Tahoe 26.6.2 with version v1.1.16, then trace the session state after the response is returned and use the attached screenshots as reference. Done means the session changes to the response-returned state without losing queued messages when stopped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100