{"version":"2.1.286","anchor":"claude-code-config-probe-env-var-short-circuits-two-startup","canonical_anchor":"claude-code-config-probe-env-var-short-circuits-two-startup","heading":"New CLAUDE_CODE_CONFIG_PROBE variable skips two startup steps","tier":"use","area":"Startup","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/claude-code-config-probe-env-var-short-circuits-two-startup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### New `CLAUDE_CODE_CONFIG_PROBE` variable skips two startup steps\n\nWhen the `CLAUDE_CODE_CONFIG_PROBE` environment variable is set, Claude Code skips two of the routines it normally runs at startup\n\n**Unclear.** It is not clear what the two skipped startup routines do or who is expected to set this variable.\n\n**What**\n\nClaude Code now checks a new environment variable, `CLAUDE_CODE_CONFIG_PROBE`. An environment variable is a named value set in your shell before a program starts. When it is set, two routines that normally run while Claude Code starts up stop early and do nothing.\n\n**Why**\n\nThis looks like a probe mode: a way to start Claude Code just to inspect its configuration without the usual startup side effects. Nothing else in Claude Code reads the variable.\n\n- Area: Startup\n- Names: `CLAUDE_CODE_CONFIG_PROBE`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5"}