{"version":"2.1.223","anchor":"remote-control-bridge-registers-a-persistent-machine-id","canonical_anchor":"remote-control-bridge-registers-a-persistent-machine-id","heading":"Remote-control bridge registers a persistent machine id","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/remote-control-bridge-registers-a-persistent-machine-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Remote-control bridge registers a persistent machine id\n\nYour install now gets a stable machine ID that identifies it when connecting through the remote-control bridge.\n\n**What**\n\nBridge environment registration now identifies the machine with a stable per-install UUID rather than only a name.\n\n**Details**\n\n- The id is resolved by `getOrCreateRemoteControlMachineId`, stored in global config, generated once and re-read afterwards.\n- Sent as `machine_id` alongside `machine_name` in the POST to `\/v1\/environments\/bridge`, and in the debug log line of the same payload.\n- The field is omitted if the id could not be persisted.\n- Both the accessor and the config key are new in this build.\n\n**Evidence**\n\n`getOrCreateRemoteControlMachineId`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}