Resuming a session another process still controls can decline the takeover and tell you why.
tengu_bridge_resume_respects_local_owner Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.232: 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.
tengu_sequential_puffin Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.232: 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.232. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When you resume a transcript whose remote-control session is still served by another local process, Claude Code can now decline to take it over, logging that it is "not taking it over (/remote-control here moves it)". A second gate decides whether a restored session must reattach or may mint a fresh one.
tengu_bridge_resume_respects_local_ownerguards the decline-and-log behaviour, recordingrestored_pointer_held_locally.tengu_sequential_puffinchooses between reattach-or-fail and falling back to a new session.- Both default to on when no remote config value is present; the real values come from the server, so this build does not decide them.
tengu_bridge_resume_respects_local_owner
Strings lifted out of the shipped bundle, so the claim above can be checked against them.