[Bug] Chat messages arrive out of order and delayed during long-running commands

Resolved 💬 1 comment Opened Jun 3, 2026 by Pluglug Closed Jul 7, 2026

Bug Description
[Summary]
Chat messages sent by the user during a long-running command arrive at the assistant in an order different from the order they were sent (and with a delay).

[Environment]

  • Claude Code (CLI)
  • macOS (Darwin 25.3.0, Apple Silicon)
  • Model: Claude Opus 4.8

[Reproduction Steps]

  1. Have the assistant execute a long Bash command (approximately 90-190 seconds).
  2. During execution, the user sends multiple messages in sequence.
  • 1st message: Message containing a file path
  • 2nd message: Short message
  • Continue sending messages thereafter.

[Expected Behavior]
Messages arrive at the assistant in the order they were sent.

[Actual Behavior]
The short message sent later arrived at the assistant before the earlier message containing the file path.
The message containing the file path took a long time to arrive and arrived considerably later (reversed order + delay).
The assistant's receiving log also confirmed that the sending order and arrival order did not match. [Impact]

Because the prerequisite information (file paths, etc.) arrives later, the context may not match,
and there is a risk that processing will proceed based on incorrect assumptions.

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 2.1.160
  • Feedback ID: fd3f7e1f-9811-4796-8862-aa207262a16a

Errors

[]

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗