{"version":"2.1.239","anchor":"remote-control-can-serve-a-reduced-tool-set-switched-off-in-","canonical_anchor":"remote-control-can-serve-a-reduced-tool-set-switched-off-in-","heading":"Remote Control can serve a reduced tool set, switched off in this build","tier":"soon","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/remote-control-can-serve-a-reduced-tool-set-switched-off-in-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Remote Control can serve a reduced tool set, switched off in this build\n\nRemote Control could expose a smaller tool set, but no code asks for it.\n\n**What**\n\nThe Remote Control setup now picks which tools it exposes based on a new option: in \"serving remote tools\" mode it exposes only the device-name tool, otherwise it also exposes the device-id tool. The option falls back to a helper that always returns false and no code passes it, so the two-tool set is what ships.\n\n**Details**\n\n- The fallback is `function _Xr() { return !1; }`; nothing in the build supplies `isServingRemoteTools`.\n- The same setup now also passes a session-id getter into the socket client that talks to the remote device.\n\n**Evidence**\n\n`isServingRemoteTools`\n\n- Area: Remote Control\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}