{"version":"2.1.228","anchor":"garbage-numeric-env-vars-fall-back-to-defaults","canonical_anchor":"garbage-numeric-env-vars-fall-back-to-defaults","heading":"Garbage numeric env vars fall back to defaults","tier":"use","area":"Configuration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/garbage-numeric-env-vars-fall-back-to-defaults","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Garbage numeric env vars fall back to defaults\n\nNonsense values in retry, MCP output and hook timeout env vars now fall back to defaults.\n\n**What**\n\n`CLAUDE_CODE_MAX_RETRIES`, `MAX_MCP_OUTPUT_TOKENS` and `CLAUDE_CODE_SESSIONEND_HOOKS_TIMEOUT_MS` are now checked for being finite numbers before use. A non-numeric or infinite value falls back to the built-in default instead of corrupting the retry count, the MCP output token budget or the SessionEnd hook timeout.\n\n**Details**\n\n- The existing warning about a retry count being clamped to the allowed maximum is unchanged.\n\n**Evidence**\n\n`CLAUDE_CODE_MAX_RETRIES=${t} clamped to ${wNa}`\n\n- Area: Configuration\n- Names: `CLAUDE_CODE_MAX_RETRIES`, `MAX_MCP_OUTPUT_TOKENS`, `CLAUDE_CODE_SESSIONEND_HOOKS_TIMEOUT_MS`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}