{"version":"2.1.317","anchor":"new-hostmanagedrunnerchild-context-flag","canonical_anchor":"new-hostmanagedrunnerchild-context-flag","heading":"New internal setting for sessions started by a host-managed runner","tier":"soon","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/new-hostmanagedrunnerchild-context-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### New internal setting for sessions started by a host-managed runner\n\nClaude Code gained an internal setting marking a session as a child of a host-managed runner, off by default\n\n**Unclear.** Nothing shows what turns this setting on or what it changes once on.\n\n**What**\n\nClaude Code gained an internal setting, `hostManagedRunnerChild`, that marks a session as one started by a runner that a host program manages. It is off by default.\n\n**Why**\n\nIt points toward sessions run under the control of another program, but nothing visible depends on it yet.\n\n- Area: Self-Hosted Runners\n- Names: `hostManagedRunnerChild`\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: org\n- Heads-up: no\n- Present in the build but not switched on"}