{"version":"2.1.281","anchor":"bridge-session-updates-with-client-metadata-always-take-the","canonical_anchor":"bridge-session-updates-with-client-metadata-always-take-the","heading":"Bridge session updates with client_metadata always take the CCR v2 path","tier":"internal","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/bridge-session-updates-with-client-metadata-always-take-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Bridge session updates with client_metadata always take the CCR v2 path\n\nBridge session updates that include client_metadata now always go the CCR v2 way, without an organization lookup\n\n**Unclear.** The finding does not say what a bridge session is or whether a user would notice any difference.\n\n**What**\n\nWhen Claude Code updates a bridge session and the update includes `client_metadata`, it now always uses the CCR v2 update route. This happens even when that route is otherwise turned off, and no organization ID lookup is done for these updates.\n\n**Why**\n\nUpdates carrying this metadata now follow one fixed route and skip a lookup step.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}