Auto mode hangs silently when a tool call is rejected by sandbox/permissions

Summary

In auto mode, when a Bash (or other) tool call is rejected by the sandbox permission system (e.g. "Deleting pre-existing untracked files without explicit user authorization"), the session does not surface the rejection to the user or prompt for a decision. From the user's perspective it just hangs.

Observed

• Running in auto mode
• Claude issues a Bash command that the sandbox blocks with a denial message (visible in the transcript)
• Claude receives the denial and re-plans, but if Claude chooses to wait for user input, the user never sees a prompt — the UI appears idle/hung
• User had to manually interrupt and ask "you stuck?" to discover what happened

Expected

Either:

• Auto mode should prompt the user to approve/override the blocked action (same as non-auto mode), OR
• Claude should explicitly surface a blocking question to the user in chat text when it can't proceed autonomously

Environment

• Claude Code CLI, auto mode
• Platform: darwin 25.3.0
• Model: claude-opus-4-7

Impact

Silent hangs in auto mode erode trust in unattended execution — the user can't tell whether Claude is working, thinking, or actually blocked.