[DOCS] Background bash command docs omit ~45-second stuck-prompt notification

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/interactive-mode

Section/Topic

"Background bash commands" → "How backgrounding works"

Current Documentation

The docs currently say:

Claude Code supports running bash commands in the background, allowing you to continue working while long-running processes execute. Key features: Output is written to a file and Claude can retrieve it using the Read tool Background tasks have unique IDs for tracking and output retrieval Background tasks are automatically cleaned up when Claude Code exits Background tasks are automatically terminated if output exceeds 5GB, with a note in stderr explaining why

No note explains what happens when a backgrounded bash task is waiting on an interactive prompt, or that Claude Code now surfaces a notification after about 45 seconds.

What's Wrong or Missing?

Changelog v2.1.84 added this user-facing behavior:

Background bash tasks that appear stuck on an interactive prompt now surface a notification after ~45 seconds

The interactive-mode docs currently describe background tasks only as generic long-running commands. They do not explain that a backgrounded bash task can appear stalled when it hits an interactive prompt, or that Claude Code now detects this condition and notifies the user after about 45 seconds.

Without that guidance, users can misread the situation as a hung task or a Claude Code bug instead of an input-waiting background command that needs attention.

Suggested Improvement

Add a short note under "Background bash commands" clarifying that background tasks are best for non-interactive commands, and that:

If a backgrounded bash command appears stuck waiting on an interactive prompt, Claude Code surfaces a notification after about 45 seconds so you can inspect the task.

The same note should briefly explain what the notification means and point users to /tasks to review or stop the task if it cannot continue without interactive input.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/interactive-mode | Primary background bash commands reference; missing any note about stuck interactive prompts and the ~45-second notification |

Total scope: 1 page affected

Source: Changelog v2.1.84

Exact changelog entry:

Background bash tasks that appear stuck on an interactive prompt now surface a notification after ~45 seconds