fix: show the message that was typed while Claude was working

[KobeVrancken]

A message you send while Claude is working never reaches the conversation the adapter rebuilds. Found while explaining the neighbouring case in #21, and it turns out to be a bug of its own rather than a footnote.

Stacked on #21, which is stacked on #20 and #19, so this branch carries all three and the diff against main includes them. The commit to read here is the last one.

What was happening

Claude does not take a message that arrives mid-turn: it queues it, and takes it at the end of the turn it was in. The queue is the whole record. From one of my sessions, this is every record in the transcript carrying what I typed:

{"type":"attachment","uuid":"a9be3e81-…","timestamp":"2026-09-03T21:04:16.591Z",
 "attachment":{"type":"queued_command","commandMode":"prompt",
               "prompt":"I interrupt you, what happens",
               "origin":{"kind":"human"},
               "source_uuid":"eaf73e0a-ef44-4f3c-90ad-f8a2f94e09cd"}}

source_uuid resolves to nothing in the file, and no user turn ever carries the text. Eighteen seconds later Claude answers it:

21:04:34  assistant :: "Here's what happened, concretely: - **Your message arrived…"

The translator reads user turns, so it emitted nothing for the message. Paseo shows what you typed as you send it, so nothing looks wrong at the time — the cost lands on reload, where a session's conversation is rebuilt by replaying its transcript: your line is gone and Claude's answer to it is not.

Sixteen such messages across this box's transcripts, every one attachment-only.

What changed

• The queued_command attachment is read as the message it carries, when its commandMode is prompt. <task-notification> is scrubbed out of user text as it always was, so a report queued through the same attachment does not become something the user said.
• It is keyed by source_uuid, the queue's own id for the item, rather than by the record it was written in: the queue is written out again under a new record for as long as the item sits in it, and the item is the same one each time. Notification records were observed repeating that way ten times in four minutes; no human prompt has been seen to, but the id is the honest key either way.
• An agent's report queued through the same attachment — the fix: let a session let go of the agents it has finished with #21 fix — now goes through the same place, and the prompt is passed on whole rather than as a string, because 3 of the 16 are written as content blocks rather than as one.

Not covered

Only text is read out of a queued message. None of the sixteen carried an image, and a queued image would still be missing from a rebuilt conversation.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BM8mp2wkVHsyeyuuHkoXaQ