The 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.
- 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.
- The default still comes from the
tengu_cobalt_harborflag, which is off unless remote config says otherwise. - One of the possible sources, a persistent remote session, cannot be reached: the check that would select it always returns false in this build.
persistent_remote_session
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_cobalt_harbor Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.224: 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.224. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.