[Bug] Claude Code fails on long-running bash commands exceeding 10-30 minutes

Bug Description
I was on codex for a while and now it really bothers me that Claude fails miserably whenever tests take more than 10 minutes or as part of the workflow there is a bash command which takes 20-30 minutes and again, it works pretty bad.

Last issues I had were on desktop app, but feedback does not even work there. I have many use cases in game dev where a step of the plan will be bash triggering some Unity baking process which will take 30 minutes and should be blocking, yesterday the app failed multiple times even when Claude was made aware.

I never have any issues in the other directions, I am always observing and running additional agents until my time is saturated. Also not having the terminal or app focused does not mean I am not watching, quite the opposite if it's focused means I have left it running while I am away.

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.111
• Feedback ID: ad91008a-ccd9-49f2-ba94-465787b679e4

Errors

[]

The exact issue on Desktop Claude was:

• Claude knows something will take 30 minutes
• Runs it in the background
• The task never finishes, it is impossible to view terminal

On Claude Code I had lots of issues with tests:

• They often take around 10 minutes and I have higher time outs in the script itself
• It is impossible to even manually override Claude internal time out, when asked Claude reports 10 minutes it's the upper limit for tool calls
• EVERY TIME THEY TAKE MORE THAN 10 CLAUDE JUST FAILS THE TOOL CALL AND TRIES TO WORK AROUND wasting time and tokens