{"version":"2.1.224","anchor":"telemetry-for-how-remote-control-autostart-was-decided","canonical_anchor":"telemetry-for-how-remote-control-autostart-was-decided","heading":"Telemetry for how remote-control autostart was decided","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/telemetry-for-how-remote-control-autostart-was-decided","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Telemetry for how remote-control autostart was decided\n\nWhether remote control auto-started, and why, is now recorded.\n\n**What**\n\nThe autostart decision now reports both its value and where the value came from, so the reason a session did or did not start in remote-control mode is recorded.\n\n**Details**\n\n- The event records the explicit setting and its source, the default and its source, plus mirror, reattach and the resolved result of off, mirror or full.\n- The default still comes from the `tengu_cobalt_harbor` flag, which is off unless remote config says otherwise.\n- One of the possible sources, a persistent remote session, cannot be reached: the check that would select it always returns false in this build.\n\n**Evidence**\n\n`persistent_remote_session`\n\n- Flag `tengu_cobalt_harbor`: Off in both readings (read for one account on one subscription tier against v2.1.224; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}