Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.248entry #171

Claude Code v2.1.248 ·

MCP environment variables parsed once, with bounds

MCP_TOOL_TIMEOUT is parsed with a minimum of 1 and ENABLE_MCP_LARGE_OUTPUT_FILES only disables when explicitly false.

Use it now Notable Improvements
JSON All of v2.1.248
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.248,
What probably matters to youSection of the release
What

MCP and main-loop code no longer reads environment variables directly with hand-rolled parsing. MCP_TOOL_TIMEOUT is now parsed as an integer with a minimum of 1 instead of a bare greater-than-zero check, and the large-output-files guard now only kicks in when ENABLE_MCP_LARGE_OUTPUT_FILES is explicitly false rather than on any truthy string.

Details
Evidence

MCP_TOOL_TIMEOUT

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

Read from
Names in the bundleMCP_TOOL_TIMEOUTENABLE_MCP_LARGE_OUTPUT_FILES
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up MCP_TOOL_TIMEOUT, on Code in Claude Desktop on 3P. | `mcpToolTimeoutSec` | Applies your per-call MCP tool timeout to Code sessions as well, taking precedence over a user-set `MCP_TOOL_TIMEOUT`. | third-party/claude-desktop/code see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up MCP_TOOL_TIMEOUT, on Code in Claude Desktop on 3P.

See this entry in the whole of v2.1.248 →

Feedback