{"version":"2.1.224","anchor":"remote-control-autostart-decision-is-resolved-in-one-place","canonical_anchor":"remote-control-autostart-decision-is-resolved-in-one-place","heading":"Remote-control autostart decision is resolved in one place","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/remote-control-autostart-decision-is-resolved-in-one-place","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Remote-control autostart decision is resolved in one place\n\nOne resolver now decides whether Remote Control starts and in which mode, weighing flags, settings and env vars.\n\n**What**\n\nWhether the remote-control bridge starts, and whether it runs full or outbound-only, is now decided by a single resolver that weighs the `CLAUDE_CODE_REMOTE` environment variable, the `--remote-control` flag, the explicit setting, a built-in default, and the `CLAUDE_BRIDGE_REATTACH_SESSION` and `CLAUDE_BRIDGE_REATTACH_OUTBOUND_ONLY` variables.\n\n**Details**\n\n- The outcome is reported as `tengu_rc_autostart_resolved`, carrying the explicit setting and where it came from, the default and its source, and the mode that won.\n\n**Evidence**\n\n`tengu_rc_autostart_resolved`\n\n- Area: Remote Control\n- Names: `CLAUDE_CODE_REMOTE`, `--remote-control`, `CLAUDE_BRIDGE_REATTACH_SESSION`, `CLAUDE_BRIDGE_REATTACH_OUTBOUND_ONLY`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}