[BUG] Started today CC only waits 3 seconds on bash commands and continues to say interrupted after to each promp
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
This issue just started today after using CC on this machine for a good while.
It only waits 3 seconds on timed bash commands and returns to the prompt.
After a few attempts of talking to Claude it will say interrupted after to each prompt - I am not interrupting it.
I have changed nothing. I did not see Claude or Windows update. Have rebooted. Checked config. I do not see the cause.
This issue persists in an existing session or new one and in any project/directory I open it in.
What Should Happen?
It should work. :)
Error Messages/Logs
❯ Last time I ran claude code it could not make it past 3 seconds on a timed bash before returning to the prompt. I have rebooted my PC. Can you run a test bash?
● Sure, let me run a quick timed test.
● Bash(echo "Start: $(date +%T.%N)" && sleep 5 && echo "End: $(date +%T.%N)" && echo "Success - ran for 5 seconds")
⎿ Start: 11:21:52.761570159
(3s · timeout 15s)
I think you are broken. Can you see an issue with your config?
● That's consistently dying around 2-3 seconds. Let me check your Claude Code settings for anything that might be interfering.
Searched for 3 patterns, read 2 files (ctrl+o to expand)
⎿ Interrupted · What should Claude do instead?
❯ You also keep saying interrupted when I didn't interrupt you
⎿ Interrupted · What should Claude do instead?
Steps to Reproduce
Simply ask Claude to run any bash that uses its normal timeout instead of a background bash.
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.80
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
WSL (Windows Subsystem for Linux)
Additional Information
_No response_
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗