[FEATURE] Desktop app Code tab: no way to distinguish cogitation from completion

Summary

• In the desktop app's Code tab, there is no persistent indicator distinguishing "Claude is still processing" from "Claude has finished responding."
• During tool use, the scrolling activity log provides implicit feedback. But when cogitation begins (extended thinking with no tool calls), the scroll stops and the last visible message — often a status line like "Document read completed" — looks identical to a final response.
• The input field appears ready for new input, but it isn't. Typing interrupts the in-progress cogitation.
• This leads to frequent accidental interruptions during long processing stretches (10–15 minutes).

Comparison with VS Code extension

The VS Code extension has a throbbing "Thinking..." indicator with a scroll-down button that lets the user verify Claude is still working. Not ideal UX, but it communicates state. The desktop app Code tab has nothing equivalent.

Expected behavior

A visible, persistent state indicator that remains active whenever Claude is processing — especially during extended thinking periods with no tool activity. The user should never have to guess whether the session is waiting for input or still working.

Current behavior

Tool-use scroll stops. Last status message resembles a completion message. Input area appears receptive. No visual distinction from "finished." User types, interrupts cogitation, loses the in-progress work.

Environment

• Platform: Windows 11 Pro
• Claude Code Desktop App (Code tab)

Test plan

• [ ] Verify indicator remains visible during extended thinking (no tool calls)
• [ ] Verify indicator distinguishes tool-use pauses from true completion
• [ ] Verify input area visually signals when it is not yet accepting input

🤖 Generated with Claude Code