One resolver now decides whether Remote Control starts and in which mode, weighing flags, settings and env vars.
What's wrong with this entry?
Whether 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.
- 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.
tengu_rc_autostart_resolved
Strings lifted out of the shipped bundle, so the claim above can be checked against them.