{"version":"2.1.318","anchor":"output-format-sessions-with-a-runner-child-no-longer-cut-set","canonical_anchor":"output-format-sessions-with-a-runner-child-no-longer-cut-set","heading":"Cloud worker sessions get a new check on narrowing settings","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/output-format-sessions-with-a-runner-child-no-longer-cut-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Cloud worker sessions get a new check on narrowing settings\n\nCloud worker sessions add a check on narrowing settings to a list, applied when CLAUDE_CODE_ENTRYPOINT is unset or on an allowed list\n\n**What**\n\nWhen Claude Code runs as a worker in the cloud, it checks messages coming in from outside. That check now takes an extra input, and a new group of settings guards is added. A new test decides whether settings are narrowed to a list. It passes when the environment variable `CLAUDE_CODE_ENTRYPOINT`, which records how Claude Code was started, is unset or is one of an allowed set of values.\n\n**Why**\n\nThis changes how settings are passed along in managed cloud sessions, depending on how Claude Code was launched.\n\n- Area: Cloud Sessions\n- Names: `CLAUDE_CODE_ENTRYPOINT`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}