{"version":"2.1.314","anchor":"bridge-child-cli-entrypoint-env-var-claude-code-bridge-child","canonical_anchor":"bridge-child-cli-entrypoint-env-var-claude-code-bridge-child","heading":"New environment variable marks some helper processes started by Claude Code","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/bridge-child-cli-entrypoint-env-var-claude-code-bridge-child","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### New environment variable marks some helper processes started by Claude Code\n\nClaude Code now sets CLAUDE_CODE_BRIDGE_CHILD_CLI_ENTRYPOINT=1 for some helper processes it starts, and clears it otherwise\n\n**Unclear.** Nothing shows what the variable changes in the helper process.\n\n**What**\n\nClaude 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.\n\nIn 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.\n\n**Why**\n\nThis 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.\n\n- Area: Remote Control\n- Names: `CLAUDE_CODE_BRIDGE_CHILD_CLI_ENTRYPOINT`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}