{"version":"2.1.280","anchor":"new-queuetranscriptonly-user-message-kind-excluded-from-tu","canonical_anchor":"new-queuetranscriptonly-user-message-kind-excluded-from-tu","heading":"New 'queueTranscriptOnly' user-message kind excluded from turn continuation logic","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-queuetranscriptonly-user-message-kind-excluded-from-tu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New 'queueTranscriptOnly' user-message kind excluded from turn continuation logic\n\nA new queueTranscriptOnly flag on user messages is now excluded from turn-continuation logic\n\n**Unclear.** The finding does not say what produces a queueTranscriptOnly message or what user-visible effect this exclusion has.\n\n**What**\n\nClaude Code now recognizes a new kind of internal user message, marked with a `queueTranscriptOnly` flag, that is also treated as an interrupted-turn-style message. This new check runs alongside the existing turn-continuation checks and affects several places in how Claude Code decides whether a turn (one exchange between you and Claude) has finished:\n\n- the idle-check, which decides if Claude Code is currently waiting or working\n\n- the interrupted-turn detection, which decides if a turn was cut off\n\n- the main classifier that categorizes messages during this process\n\n**Why**\n\nMessages marked `queueTranscriptOnly` are now handled specially rather than being folded into the normal turn-completion logic, which should make Claude Code's sense of whether a turn is still in progress more accurate when this kind of message appears.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}