{"version":"2.1.223","anchor":"remote-control-registration-sends-a-stable-machine-id","canonical_anchor":"remote-control-registration-sends-a-stable-machine-id","heading":"Remote Control registration sends a stable 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-registration-sends-a-stable-machine-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Remote Control registration sends a stable machine_id\n\nYour machine now gets a stored id so remote sessions recognise the same workstation each time.\n\n**What**\n\nBridge environment registration now identifies the machine with a persistent id, so the same workstation is recognised across sessions.\n\n**Details**\n\n- `POST \/v1\/environments\/bridge` includes `machine_id` when one is available, alongside machine_name, directory, branch and git_repo_url\n- the id is a UUID stored in global config under the new `remoteControlMachineId` key\n- it is only handed back to callers if the config write actually succeeded, which is why the global-config save path now returns a boolean instead of nothing\n\n**Evidence**\n\n`machine_id: a.machineId`, `remoteControlMachineId`\n\n- Area: Remote Control\n- Names: `remoteControlMachineId`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}