[DOCS] VS Code docs missing "Not responding" status guidance for long-running operations

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/vs-code

Section/Topic

Monitor background processes and Claude Code never responds

Current Documentation

The VS Code docs currently say:

When Claude runs long-running commands, the extension shows progress in the status bar. However, visibility for background tasks is limited compared to the CLI. For better visibility, have Claude output the command so you can run it in VS Code's integrated terminal.

Later on the same page, the troubleshooting section says:

If Claude Code isn't responding to your prompts: 1. Check your internet connection: Ensure you have a stable internet connection 2. Start a new conversation: Try starting a fresh conversation to see if the issue persists 3. Try the CLI: Run claude from the terminal to see if you get more detailed error messages

This documents that long-running commands show progress in the status bar and gives generic recovery steps, but it does not explain any VS Code-specific Not responding status state.

What's Wrong or Missing?

Changelog v2.1.86 says:

[VSCode] Fixed extension incorrectly showing "Not responding" during long-running operations

Related changelog context from v2.1.81 says:

[VSCode] Spinner now turns red with "Not responding" when the backend hasn't responded for 60 seconds

Together, these entries confirm that Not responding is an intentional, user-visible VS Code status and that long-running operations are not supposed to trigger it.

A. The Not responding indicator is undocumented

Users are told that long-running commands show progress in the status bar, but the docs never explain that Not responding is a distinct warning state rather than the normal appearance of a long-running operation.

B. The troubleshooting guidance does not distinguish a stalled backend from legitimate long-running work

The Claude Code never responds section jumps straight to generic recovery steps and does not tell users how the extension's status bar should behave during normal long-running commands versus an actual responsiveness problem.

Suggested Improvement

Add a short Status bar states note under Monitor background processes that explains:

• long-running commands should continue showing normal progress in the VS Code status bar
• Not responding means the extension has not heard from the backend for about 60 seconds
• this warning is not the expected state for ordinary long-running operations
• if the warning appears, users should follow the troubleshooting steps or switch to the CLI for more detailed diagnostics

Also update Claude Code never responds to cross-reference that status-bar explanation instead of only listing generic recovery steps.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/vs-code | Monitor background processes and Claude Code never responds omit the meaning of the VS Code Not responding indicator |
| https://code.claude.com/docs/en/ide-integrations | Same VS Code extension content is published under this URL as well |

Total scope: 2 pages affected

Source: Changelog v2.1.86

Entry: [VSCode] Fixed extension incorrectly showing "Not responding" during long-running operations

Related changelog context: v2.1.81 — [VSCode] Spinner now turns red with "Not responding" when the backend hasn't responded for 60 seconds