{"version":"2.1.309","anchor":"control-responses-can-be-tagged-for-some-requests","canonical_anchor":"control-responses-can-be-tagged-for-some-requests","heading":"Some replies sent over the session bridge now carry an extra marker","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/control-responses-can-be-tagged-for-some-requests","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Some replies sent over the session bridge now carry an extra marker\n\nFor some requests, Claude Code now adds an extra marker to its replies over the bridge that connects the interactive session to another client\n\n**What**\n\nClaude Code has a bridge: a connection that passes messages between your interactive session and another program. When that program sends a control request (an instruction to the session, rather than a chat message), Claude Code sends back a reply. For some requests, that reply now carries an extra marker. Other replies are sent unchanged, as before. This happens in two places where replies are sent.\n\n**Why**\n\nThis changes what the bridge sends back for certain requests. It matters mainly to programs that talk to Claude Code over the bridge and read its replies.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}