{"version":"2.1.269","anchor":"claude-code-bridge-child-artifact-new-artifact-inheritance","canonical_anchor":"claude-code-bridge-child-artifact-new-artifact-inheritance","heading":"CLAUDE_CODE_BRIDGE_CHILD_ARTIFACT: new artifact-inheritance signal for bridge child sessions","tier":"internal","area":"Bridge Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/claude-code-bridge-child-artifact-new-artifact-inheritance","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### CLAUDE_CODE_BRIDGE_CHILD_ARTIFACT: new artifact-inheritance signal for bridge child sessions\n\nNew CLAUDE_CODE_BRIDGE_CHILD_ARTIFACT env var signals artifact settings to bridge child sessions\n\n**What**\n\nA new environment variable, set to \"1\" automatically when Claude Code spawns a bridge child session, is now checked alongside `CLAUDE_CODE_ARTIFACT` and a `CLAUDE_CODE_BRIDGE_CHILD_AUTO_DEFAULT` flag. Together these decide whether the artifact tool reports itself as switched off by default (`sdk_default_off`) inside that child process.\n\n**Why**\n\nThis lets a child session spawned via a bridge inherit or determine its own artifact-tool availability correctly, rather than falling back to a default that might not fit a child process's context, building on the existing chain of checks (policy, provider type, traffic restrictions, and env overrides) that already decides whether the artifact tool is offered.\n\n- Area: Bridge Sessions\n- Names: `CLAUDE_CODE_BRIDGE_CHILD_ARTIFACT`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}