Preflight Checklist
What's Wrong?
In Claude Cowork (desktop app), two related UI issues make the app nearly unusable during longer sessions:
Issue 1: Responses don't render until the user types something
Claude's response completes processing but the UI does not display it. The response only appears after the user types a new message. This means the user cannot read Claude's output and cannot know what to do next — they only discover responses retroactively after sending a follow-up message.
Issue 2: "Working through a complex response" spinner hangs indefinitely
During sessions with multiple tool calls or background processing (file reads, Bash commands, agent tasks), the UI shows "Working through a complex response..." and hangs for several minutes with no progress. The response may have completed on the backend but the UI never updates.
Combined effect:
The user cannot have a functional conversation. They cannot see responses, cannot answer questions Claude asks, and lose typed input when the UI is stuck. This occurred repeatedly in a single session today (2026-02-19) causing significant workflow disruption and lost context.
Environment:
- App: Claude Cowork (desktop, macOS)
-
- Session type: Long session with multiple tool calls (Bash, file reads, Notion MCP, Task agents)
-
-
- Vault: Obsidian vault mounted as working directory
What Should Happen?
Responses should render immediately when Claude finishes generating them, without requiring user input to trigger display. The "Working through a complex response" state should either resolve in a reasonable time or surface an error — it should never hang indefinitely with no feedback or recovery option.
Error Messages/Logs
Steps to Reproduce
- Open Claude Cowork (macOS desktop app)
-
- Mount an Obsidian vault as the working directory
-
- Start a long session involving multiple tool calls (Bash commands, file reads/writes, Notion MCP calls, Task agent spawning)
-
- Claude completes a response after tool use
-
- Bug 1: The response does not appear in the UI. The chat window shows no new message. Type anything in the input box — the response appears only after sending the new message.
-
- For Bug 2: During a session with heavy processing (multiple sequential tool calls), observe the UI display "Working through a complex response..." and wait. The spinner persists for 3-5+ minutes with no resolution and no error message. The UI provides no way to cancel or recover.
Notes:
- Both bugs appear more frequently as session length increases (longer context window)
-
- Bug 1 appears to be a rendering/state update issue — the response exists but the UI doesn't reflect it
-
-
- Bug 2 may be related to the UI losing sync with the backend during long processing chains
-
-
-
- Reloading the app clears the session context, so there is no viable recovery path
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
No response
Claude Code Version
2.1.45 (Claude Code) — running via Claude Cowork desktop app
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
No response
Preflight Checklist
What's Wrong?
In Claude Cowork (desktop app), two related UI issues make the app nearly unusable during longer sessions:
Issue 1: Responses don't render until the user types something
Claude's response completes processing but the UI does not display it. The response only appears after the user types a new message. This means the user cannot read Claude's output and cannot know what to do next — they only discover responses retroactively after sending a follow-up message.
Issue 2: "Working through a complex response" spinner hangs indefinitely
During sessions with multiple tool calls or background processing (file reads, Bash commands, agent tasks), the UI shows "Working through a complex response..." and hangs for several minutes with no progress. The response may have completed on the backend but the UI never updates.
Combined effect:
The user cannot have a functional conversation. They cannot see responses, cannot answer questions Claude asks, and lose typed input when the UI is stuck. This occurred repeatedly in a single session today (2026-02-19) causing significant workflow disruption and lost context.
Environment:
What Should Happen?
Responses should render immediately when Claude finishes generating them, without requiring user input to trigger display. The "Working through a complex response" state should either resolve in a reasonable time or surface an error — it should never hang indefinitely with no feedback or recovery option.
Error Messages/Logs
Steps to Reproduce
Notes:
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
No response
Claude Code Version
2.1.45 (Claude Code) — running via Claude Cowork desktop app
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
No response