{"version":"2.1.281","anchor":"bridgerc-child-roles-artifact-gate-extended-to-attended-se","canonical_anchor":"bridgerc-child-roles-artifact-gate-extended-to-attended-se","heading":"Remote Control child sessions: auto mode can now override settings, and artifacts reach attended sessions","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/bridgerc-child-roles-artifact-gate-extended-to-attended-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote Control child sessions: auto mode can now override settings, and artifacts reach attended sessions\n\nRemote Control child sessions now honour the auto-over-settings flag, and the artifact option extends to attended sessions\n\n**Unclear.** The finding does not say what the check that now accepts either gate controls.\n\n**What**\n\nRemote Control can start child sessions on your machine. Several flags decide how those child sessions are set up, and this release changes how they are applied.\n\n- `autoOverSettings` is now actually used. Before, Claude Code computed it from `tengu_bridge_child_auto_over_settings` and then always returned false, so the flag had no effect. Now a child session that gets auto mode by default through `tengu_bridge_child_auto_mode` can also have auto mode take priority over the permission mode set in your settings. Auto mode skips normal approval prompts.\n\n- The `artifact` option now applies to attended child sessions as well as project-thread children. It is still behind `tengu_bridge_rc_child_artifact`.\n\n- A related check now passes when either `tengu_bridge_child_auto_mode` or `tengu_bridge_rc_child_artifact` is on.\n\nNothing has been read yet about `tengu_bridge_rc_child_artifact`, `tengu_bridge_child_auto_over_settings`, `tengu_bridge_child_auto_mode` or `tengu_bridge_child_machine_settings`.\n\n**Why**\n\nIf you use Remote Control child sessions, auto mode may now win over the permission mode in your settings where these flags are on. Before, the setting was ignored whatever the flag said.\n\n- Flag `tengu_bridge_rc_child_artifact`: Not enough to say (read for one account on one subscription tier against v2.1.281; this account: no value returned, anonymous baseline: no value returned, 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- Flag `tengu_bridge_child_auto_over_settings`: Not enough to say (read for one account on one subscription tier against v2.1.281; this account: no value returned, anonymous baseline: no value returned, 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- Flag `tengu_bridge_child_auto_mode`: Not enough to say (read for one account on one subscription tier against v2.1.281; this account: no value returned, anonymous baseline: no value returned, 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- Flag `tengu_bridge_child_machine_settings`: Not enough to say (read for one account on one subscription tier against v2.1.281; this account: no value returned, anonymous baseline: no value returned, 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."}