After you log back in, Remote Control can turn itself back on without you re-running the command.
tengu_bridge_auth_revive Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.225: 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.
Read once, for one account on one subscription tier, against v2.1.225. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A polling watcher notices a fresh OAuth credential for the same account and re-enables Remote Control without you having to run /remote-control again.
- Polls on a 5 minute interval.
- Disarms itself if the new credential belongs to a different account.
- Reattach and archive paths re-verify the signed-in account before acting.
- Gated on
tengu_bridge_auth_revivewith fallback!0; with the kill switch off the watcher still polls but performs no unattended revive.
tengu_bridge_repl_auth_revive
Strings lifted out of the shipped bundle, so the claim above can be checked against them.