TaskOutput block=true locks out user with no escape

Summary

When Claude uses TaskOutput with block=true, the user is completely locked out of the conversation until the task completes. ESC key does not work. The only way to regain control is to kill the background task.

Expected behavior

• ESC should interrupt the blocking call
• Or: block=false should be the default
• Or: Claude should never use block=true for long-running tasks

Actual behavior

• User sees "Waiting for task (esc to give additional instructions)"
• ESC does nothing
• User cannot communicate with Claude
• Must kill the task externally to regain control

Impact

User repeatedly asked Claude to stop using blocking calls. Claude acknowledged and apologized multiple times but continued the behavior. User has no mechanism to enforce this preference.

Suggested fixes

1. Make block=false the default
2. Make ESC actually work during blocking waits
3. Add a user setting to disable blocking TaskOutput calls
4. Add timeout with automatic fallback to non-blocking

Reproduction

Ask Claude to run a long task, Claude calls TaskOutput with block=true, user is locked out for duration.