No processing indicator when resuming an interrupted thread
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Ref: X thread
My Mac fell asleep mid-session while Codex was reviewing some Salesforce components. When I came back and tried to resume, I sent two messages and got zero feedback, and it didn't indicate the "working" state, no sidebar badge, nothing. Responses did come through eventually, just no indication anything was happening in the meantime. If I have time Sunday or Monday I can dig through it and see what caused it.
Small thing, but Claude Code has the same kind of issue where if you come back to a dropped session or it updated the VS Code extension while you were away, sometimes it'll show a working indicator but the process never actually ran. Either way, without that feedback you have no idea if you should wait, retry, or just start over.
Would be nice to have some visible processing state when resuming an interrupted thread. Again minor issue, beyond that everything is smooth. Not having to use an app that freezes or stutters is refreshing.
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
The issue names no files or tests. Start by reproducing an interrupted thread after the app resumes, then trace the thread's processing state and its visible indicator; done means the resumed thread clearly shows that work is in progress and gives usable feedback while waiting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100