Garbage numeric env vars fall back to defaults

Nonsense values in retry, MCP output and hook timeout env vars now fall back to defaults.

Use it nowTier: how much it should matter to you

3Useful: my rating, 1 to 5

2Signal: worth watching, 1 to 5

ConfigurationArea: what it touches

Bug FixesKind: in v2.1.228, 11 Aug 26

What probably matters to youSection of the release

What

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.

Details

The existing warning about a retry count being clamped to the allowed maximum is unchanged.

Evidence

CLAUDE_CODE_MAX_RETRIES=${t} clamped to ${wNa}

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from

The build it came inv2.1.228

11 Aug 2026 · 245 entries, this one is #57.

Either side of it

Open the release →

Names in this entry

envCLAUDE_CODE_MAX_RETRIES
Override the number of times to retry failed API requests (default: 10). Capped at 15 as of v2.1.186; as of v2.1.199, CLAUDE_CODE_RETRY_WATCHDOG raises the default and removes the cap. For unattended sessions that need to wait through longer outages, set CLAUDE_CODE_RETRY_WATCHDOG instead
envMAX_MCP_OUTPUT_TOKENS
Nonsense values in retry, MCP output and hook timeout env vars now fall back to defaults.
envCLAUDE_CODE_SESSIONEND_HOOKS_TIMEOUT_MS
Nonsense values in retry, MCP output and hook timeout env vars now fall back to defaults.
hookSessionEnd
When a session terminates

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.