[BUG] Cowork: final assistant message invisible until user sends next prompt
Status Fixed / completed
Maintainer reply None cached
Activity 5 comments · opened Feb 19, 2026 · closed Feb 22, 2026
Bug
When Claude finishes a multi-step tool-call sequence in Cowork mode, the final assistant text message is generated but not rendered in the UI. The spinner stops, the todo list shows all tasks complete, but the response text is invisible. It only appears after the user types a new message and presses Enter.
Environment
- Platform: macOS (Mac Mini, Apple Silicon)
- Mode: Cowork
- Reproducibility: Consistent — happens reliably after long tool-call sequences (5+ tool calls)
Steps to Reproduce
- Start a Cowork session with a mounted folder
- Ask Claude to perform a multi-step task (e.g., "fix all failing tests" involving 10+ tool calls via Desktop Commander)
- Wait for Claude to finish — spinner stops, todo list shows complete
- Observe: no text response visible
- Type anything and press Enter
- Claude's completed response from step 3 now appears
Expected Behavior
The final assistant message should render immediately when generation completes, without requiring a new user input event to trigger the UI flush.
Actual Behavior
The assistant message is buffered/held and only displayed after the next user interaction (any keypress + Enter). The message content is correct when it does appear — it's purely a rendering timing issue.
Notes
- The todo list widget updates in real-time during the task — only the final text message is affected
- This appears to be a frontend message rendering lifecycle issue, not a backend/generation problem
- Observed consistently across multiple sessions over several days
5 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Checked all three suggested duplicates (#26878, #26876, #26881) — they are all macOS-specific. My issue is on Windows 11 Pro (Surface Laptop Studio, Build 26200). This appears to be the Windows equivalent of the same frontend rendering problem, but has not been reported for Windows before. Not a duplicate — please keep open.
Exact the same here. What should we do?
This bug was fixed in a release earlier this week, closing this one out. Thanks for using Cowork 🙇
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.