Improve Progress Communication for Long-Running Operations

Improve Progress Communication for Long-Running Operations

Priority: HIGH

Problem:
During long-running commands (5+ minutes), Claude Code is silent. User doesn't know if AI is stuck, waiting, or making progress. Observed multiple 5-minute timeouts with no feedback.

Current Behavior:

Execute command with 5-minute timeout
Complete silence until timeout or completion
User left wondering what's happening
Expected Behavior:

For commands >30 seconds, provide periodic updates
"Build submitted, waiting for EAS... 1 minute elapsed"
"Still running... 2 minutes elapsed, this is normal for iOS builds"
Show that AI is aware time is passing
Impact:

Poor user experience
User doesn't know if they should interrupt or wait
Creates anxiety about whether system is working
Suggested Implementation:

For any Bash command with timeout >30s, provide progress updates
Use BashOutput tool to check for new output periodically
Even if no new output, acknowledge time passing
Set expectations: "iOS builds typically take 3-5 minutes"