You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(chat): place mid-turn messages where claude read them
A queued bubble was appended where the user hit enter — mid-stream of
whatever claude was already saying — and stayed there, so the
conversation read as if the interjection came before content it was
actually sent after.
Two halves:
* Live: the requesting boundary now moves formerly-queued entries to
the tail as it clears isQueued. Relative order among several queued
entries is kept, and when they're already last the array comes out
identical, so nothing visibly moves in the common case.
* Reload: claude records a mid-turn interjection as a queued_command
attachment rather than a user record, positioned at the drain
boundary. parseTranscriptEntries skipped all attachments, so every
message sent while the agent was working vanished from the
scrollback on reload. Seed those as user entries; other attachment
subtypes stay ignored.
Verified against a live session: the seeded record lands between the
tool_result it interrupted and the reply that answers it, matching the
live ordering.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments