[BUG] API Error: 400 due to tool use concurrency issues. Run /rewind to recover the conversation.
Resolved 💬 17 comments Opened Oct 12, 2025 by Vhailors Closed Oct 21, 2025
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?
Randomly every 15 minutes of usage I've got this, can't do any more complicated prompt without trigger this. It's making a CC unusable!
API Error: 400 due to tool use concurrency issues. Run /rewind to recover the conversation.
What Should Happen?
I should be able to work without error
Error Messages/Logs
Steps to Reproduce
- Write any more complicated prompt
- Wait CC to crash
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.0.14
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
WSL (Windows Subsystem for Linux)
Additional Information
_No response_
17 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Claude code asked me to report this same issue I'm seeing as well so I'm adding this comment here as I am also receiving this issue making Claude Code unusable.
When reporting, include:
This appears to be an issue with how Claude Code handles parallel tool calls in recent versions. The development team will need to investigate the API rate limiting or concurrency
handling on their end.
More from Claude:
Environment:
Error Type: 400 invalid_request_error
Symptom: Conversation state becomes corrupted where tool_use blocks are sent without corresponding tool_result blocks in the conversation history.
Frequency: Multiple times over the last few days
Usage Pattern: Asking general questions in Ubuntu instance + questions about multiple repositories in VS Code
Debug Log Evidence: Available in ~/.claude/debug/ directory showing repeated instances of tool_use/tool_result mismatch
Impact: Conversation becomes unrecoverable and requires /rewind to restore
This is clearly a state management bug in how Claude Code tracks tool calls and results across the conversation history, especially when handling multiple parallel tool invocations.
My experience: /rewind doesn't help and the conversation is unrecoverable.
API Error: 400 due to tool use concurrency issues. Run /rewind to recover the conversation.
I'm getting the same issue. I'm using the Visual Studio Code extension, and there doesn't seem to be a /rewind command. My only option is to start a new conversation and try to continue from the previous one...
Facing the same, and it is happening since last claude-code update.
I’m facing the same issue—this problem has been occurring since the last update of the Claude Code extension.
Error:
API Error: 400 due to tool use concurrency issues. Run /rewind to recover the conversation.However, when I try using the
/rewindcommand, nothing happens; there seems to be no command available.Running into this as well as of the last update and my suspicions align with Jeff; the conversation seems to be in an unrecoverable bad state.
Also confirming that this has been happening since the last updates.
I've started running into this several times a day. It completely breaks my workflow.
This shit is stopping in the middle of the work.
API Error: 400 due to tool use concurrency issues. Run /rewind to recover the conversation.
+1, and this is the infuriating part... It says to use
/rewindwhich doesn't even exist in the native UI version, doesn't give any guidance about how to find what to restore it to, and/rewindin the terminal version doesn't actually fix anything for me, the conversation is dead and unrecoverable from that point.that is really annoying and counter-productive. In fact, all explanations and guidance you do through the session just gets lost
The cause(at least one of them) is returning "deny" in a json block in pretooluse hooks. Use sys.exit(2) instead and send the error via print and stderr to bypass this error.
Anthropic should start paying me for fixing there garbage code.
This is what happens when you let AI write your tools.
AI slop.
I guess that's why there are currently 4.4k open issues on this repo (4.3k are bot spam)
An another note: I've wasted so much time clicking "Yes" or "Yes, and don't ask me again" every time Claude wants to run a python command:
Maybe I don't know the syntax for this or how to just say "Shutup and do it!" but at this point, I'm just getting frustrated!
I keep doing it because:
reporting this iOS (15.6.1) + vscode using the Claud.ai add-on.
After reporting this issue just a few days ago, I see this post: Making Claude Code more secure and autonomous with sandboxing \ Anthropic
I have yet to see the benefit of this, but I'm already excited to see this being addressed!
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.