{"version":"2.1.281","anchor":"remote-control-bridge-exposes-new-internal-metadata-and-drop","canonical_anchor":"remote-control-bridge-exposes-new-internal-metadata-and-drop","heading":"Remote-control bridge exposes new internal metadata and drop counters","tier":"internal","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-control-bridge-exposes-new-internal-metadata-and-drop","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote-control bridge exposes new internal metadata and drop counters\n\nThe Remote Control bridge gains internal metadata reporting and counters for dropped updates\n\n**Unclear.** The finding does not say whether any of this is visible to someone using Remote Control.\n\n**What**\n\nThe bridge is the connection that Remote Control uses between Claude Code and the remote side. It gains four new internal pieces:\n\n- `reportInternalMetadata`, for sending internal metadata\n\n- `droppedDurableBatchCount`, a count of dropped durable batches\n\n- `flushWorkerState`, for pushing out the worker's current state\n\n- `droppedWorkerStatePatchCount`, a count of dropped worker-state updates\n\nThe callback that runs when the bridge is ready now also receives the result of the initial setup step.\n\n**Why**\n\nThese are internal plumbing. The two counters mean the bridge now keeps track of how many updates it failed to deliver rather than losing them silently.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}