{"version":"2.1.299","anchor":"queue-operations-are-written-to-the-owning-sessions-transcr","canonical_anchor":"queue-operations-are-written-to-the-owning-sessions-transcr","heading":"Queued messages are now saved to the session they belong to","tier":"internal","area":"Message Queue","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/queue-operations-are-written-to-the-owning-sessions-transcr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Queued messages are now saved to the session they belong to\n\nA queued message belonging to another session is now written to that session's transcript instead of the current one\n\n**What**\n\nWhile Claude is busy, messages you send wait in a queue. Claude Code saves changes to that queue in a session's transcript, the file that records the conversation. When a queue entry belongs to a different session than the current one, it is now written to that session's transcript, but only if that file already exists. These writes happen one at a time, in order.\n\n**Why**\n\nQueued messages should no longer end up recorded in the wrong session's history.\n\n- Area: Message Queue\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}