Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

CLAUDE_CODE_BRIDGE_CHILD_ARTIFACT: new artifact-inheritance signal for bridge child sessions

New CLAUDE_CODE_BRIDGE_CHILD_ARTIFACT env var signals artifact settings to bridge child sessions

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaBridge Sessionswhat it touches
KindInternal Changesin v2.1.269,
Under the hood No documentation found

New CLAUDE_CODE_BRIDGE_CHILD_ARTIFACT env var signals artifact settings to bridge child sessions

What

A 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.

Why

This 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.

Read from
Names in the bundleCLAUDE_CODE_BRIDGE_CHILD_ARTIFACT
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_BRIDGE_CHILD_ARTIFACT

See this entry in the whole of v2.1.269 →