[BUG] Status indicator verbs not visible during processing in VS Code extension
What's Wrong?
Description
The animated status verbs (e.g. "Thinking...", "Reading...", "Editing...") that normally appear in the input area while Claude is working are frequently not visible. This makes it impossible to tell whether Claude is actively processing or has finished and is waiting for input.
Steps to reproduce
Send a message or request that triggers tool calls (file reads, edits, etc.)
Observe the input area — the status indicator verbs are often missing
The issue is intermittent but has become noticeably more frequent in the last few days
Expected behaviour
The status indicator should consistently show activity verbs while Claude is processing, reading files, or generating a response.
Actual behaviour
The input area appears idle/empty even while Claude is actively working. There is no visual feedback until the response appears. This is particularly problematic during longer operations where multiple tool calls are involved.
Environment
VS Code extension (Claude Code)
macOS Darwin 25.3.0
Model: Claude Opus 4.6 (1M context)
Impact
Without the status indicator, it's difficult to know whether to wait for a response or whether Claude has silently finished. This leads to unnecessary interruptions and confusion during iterative development workflows.
What Should Happen?
Claude Code window in VSCode (extension) should have visible animated verbs when it's working.
Error Messages/Logs
None
Steps to Reproduce
Send a message or request that triggers tool calls (file reads, edits, etc.)
Observe the input area — the status indicator verbs are often missing
The issue is intermittent but has become noticeably more frequent in the last few days
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
previous to Claude Opus 4.6 (1M context)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗