[BUG] Claude Code - Teleport Session from Web to Local Fails with: API Error: 400 due to tool use concurrency issues. Run /rewind to recover the conversation.

Status Closed — not planned

Maintainer reply None cached

Activity 13 comments · opened Nov 19, 2025 · closed Feb 27, 2026

Found 4 possible duplicate issues:

https://github.com/anthropics/claude-code/issues/5934
https://github.com/anthropics/claude-code/issues/8514
https://github.com/anthropics/claude-code/issues/8108
https://github.com/anthropics/claude-code/issues/8763

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?

I have the same issue as 8763 on Version: 2.0.46 immediately after teleporting 'claude code on the web' session into Ubuntu server inside cloned repo.
Feedback ID: e42d62e3-7543-477a-acea-d8ebe37fa510

What Should Happen?

One should be able to communicate with Claude in Claude code after teleporting their session

Error Messages/Logs

API Error: 400 due to tool use concurrency issues. Run /rewind to recover the conversation.

Steps to Reproduce

Start a session in Claude Code on the Web
Teleport the session into cloned repo on an Ubuntu server

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.46

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

13 Comments

github-actions[bot] · 9 months ago

Found 3 possible duplicate issues:

This issue will be automatically closed as a duplicate in 3 days.

If your issue is a duplicate, please close it and 👍 the existing issue instead
To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

wey-gu · 9 months ago

I found the mitigation to save my long conversation...

rewind to previous checkpoints, like the -2, if still hit this 400 issue, go -3, if not ok, go -4
continue your conversation there

brettc · 9 months ago

I just had this same problem with the latest version of claude 2.0.54. So it is still there.

dingkwang · 9 months ago

Still has the problem with 2.0.55 using aws bedrock sonnet

dingkwang · 8 months ago

Still has the problem with 2.0.58 using aws bedrock sonnet

fabboe · 8 months ago

I also hit this today with several session I wanted to teleport from Claude Code cloud env.

emanuel248 · 8 months ago

Updated to latest version 2.0.60 after hitting this error multiple times today. It seems that the conversation itself triggers that, as soon as i try to resume the same convo after restarting it throws this.
What I did to finish the job:

copy&pasted the convo into a new one, this continued a few steps then broke down again, did this a few times to finish all steps.

risjain · 8 months ago

Can confirm that the issue persists wtih v2.0.64. I am on macos 14.

olilarkin · 8 months ago

just hit this

sleepy-zone · 7 months ago

I noticed that when using the Opus model, in the JSONL-formatted message history, tool_use messages get merged into a single assistant message, but the corresponding tool_result messages still appear as separate user messages. This causes a 400 error: "Each tool_use block must have a corresponding tool_result block in the next message." When I manually merged the tool_result blocks into a single user message, the error disappeared.

ss-napier · 7 months ago

Hey there, just faced this issue on v2.1.19 claude vscode extension.
it frequently happened every 2 action from claude.

even after following above, it still keeps saying below error

API Error: 400 due to tool use concurrency issues.

reverting back to v2.1.17 fix the issue for now.

github-actions[bot] · 6 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

github-actions[bot] · 5 months ago

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.