{"version":"2.1.224","anchor":"remote-control-registration-reports-a-bridge-epoch","canonical_anchor":"remote-control-registration-reports-a-bridge-epoch","heading":"Remote-control registration reports a bridge epoch","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/remote-control-registration-reports-a-bridge-epoch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Remote-control registration reports a bridge epoch\n\nRemote control registration and heartbeats now include an identifier for the current bridge lifetime.\n\n**What**\n\nRegistration and heartbeat payloads sent by the remote-control bridge now include a `bridge_epoch` value identifying the current bridge lifetime.\n\n**Details**\n\n- The special case that pushed `thinking_tokens` system messages straight into the bridge SDK stream, along with its dedicated error log, was removed; those messages now go through the normal enqueue path.\n\n**Evidence**\n\n`bridge_epoch`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}