Follow Discord
Sweep 30 Oct 2026 · 01:02Z Build v2.1.314 532 read Stable v2.1.308 Latest v2.1.314 Next v2.1.314 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.314 ·

New environment variable marks some helper processes started by Claude Code

Claude Code now sets CLAUDE_CODE_BRIDGE_CHILD_CLI_ENTRYPOINT=1 for some helper processes it starts, and clears it otherwise

Under the hood No documentation found Internal Changes
JSON All of v2.1.314
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
Internal ChangesKind: in v2.1.314,
Internal ChangesSection of the release

Unclear Nothing shows what the variable changes in the helper process.

What

Claude Code can start a separate helper process through what it calls a bridge. When it starts one in a particular mode, it now sets the environment variable CLAUDE_CODE_BRIDGE_CHILD_CLI_ENTRYPOINT to 1 for that process. An environment variable is a named value a program passes to the programs it starts.

In other cases, Claude Code clears the variable for the helper process. This means a value set in the parent process does not carry over into the child.

Why

This looks like a new mode for helper processes, alongside other variables with similar names. Because the variable is cleared when it does not apply, setting it yourself before starting Claude Code will not pass it on.

Read from
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtNothing shows what the variable changes in the helper process.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_BRIDGE_CHILD_CLI_ENTRYPOINT

See this entry in the whole of v2.1.314 →

Feedback