Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.228 Home All releases ←olderv2.1.227 v2.1.229newer→
Claude Code v2.1.228

Garbage numeric env vars fall back to defaults

Use it now
Useful3 Signal2
Configuration

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

CLAUDE_CODE_MAX_RETRIESMAX_MCP_OUTPUT_TOKENSCLAUDE_CODE_SESSIONEND_HOOKS_TIMEOUT_MS
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.

Related

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

See this entry in the whole of v2.1.228 →