{"version":"2.1.225","anchor":"remote-control-auto-revive-after-re-login","canonical_anchor":"remote-control-auto-revive-after-re-login","heading":"Remote Control auto-revive after re-login","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/remote-control-auto-revive-after-re-login","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Remote Control auto-revive after re-login\n\nAfter you log back in, Remote Control can turn itself back on without you re-running the command.\n\n**What**\n\nA polling watcher notices a fresh OAuth credential for the same account and re-enables Remote Control without you having to run \/remote-control again.\n\n**Details**\n\n- Polls on a 5 minute interval.\n- Disarms itself if the new credential belongs to a different account.\n- Reattach and archive paths re-verify the signed-in account before acting.\n- Gated on `tengu_bridge_auth_revive` with fallback `!0`; with the kill switch off the watcher still polls but performs no unattended revive.\n\n**Evidence**\n\n`tengu_bridge_repl_auth_revive`\n\n- Flag `tengu_bridge_auth_revive`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.225; this account: on, anonymous baseline: on, compiled default: on) 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- Names: `\/remote-control`, `tengu_bridge_auth_revive`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 0\/5"}