{"version":"2.1.269","anchor":"new-bridge-child-env-vars-for-auto-permission-mode-and-artif","canonical_anchor":"new-bridge-child-env-vars-for-auto-permission-mode-and-artif","heading":"New bridge-child env vars for auto permission mode and artifact publishing","tier":"use","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-bridge-child-env-vars-for-auto-permission-mode-and-artif","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New bridge-child env vars for auto permission mode and artifact publishing\n\nNew env vars let a bridge-spawned child session default to auto permission mode and force-enable artifacts\n\n**What**\n\nTwo new environment variables control sessions spawned as a \"bridge child\" (a worker session launched by another Claude Code process):\n\n- `CLAUDE_CODE_BRIDGE_CHILD_AUTO_DEFAULT` makes the child session default its permission mode to `auto`, overriding the normal default-mode selection.\n\n- `CLAUDE_CODE_BRIDGE_CHILD_ARTIFACT` forces the artifact-publishing feature on for that child session, alongside the existing `CLAUDE_CODE_ARTIFACT` variable. The code that reports artifacts as off by default for SDK usage (`sdk_default_off`) now also checks that this new variable is unset before reporting that reason.\n\nBoth variables are explicitly cleared on a spawned child's environment and then set to `1` only when the parent process determines they should apply.\n\n**Why**\n\nThis lets a parent process spawning bridge-child sessions control two behaviors \u2014 permission mode and artifact availability \u2014 that would otherwise default to more restrictive settings for SDK\/bridge-style sessions.\n\n- Area: Sessions\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}