CLAUDE LABJP
2.1.268 — The headline in this release is not a feature. It is a fix for a bug that had been breaking compatible endpoints since 2.1.265BASE_URL — Third-party Anthropic-compatible endpoints behind ANTHROPIC_BASE_URL were failing every turn with HTTP 400. Upgrade before you touch your configWEBFETCH — WebFetch no longer waits forever on a server that keeps the response open. It now gives up after 300 seconds, tunable via CLAUDE_CODE_WEBFETCH_DEADLINE_MSSECRET — Secrets resolved from ${VAR} placeholders in MCP configs were being printed by /mcp and claude mcp list. Worth knowing if you share your screenCPU — A busy loop that pinned a core during long idle sessions is fixed, so that fan you could not explain may finally settle downRESUME — --continue and --resume now show the conversation right away instead of waiting on SessionStart hooks2.1.268 — The headline in this release is not a feature. It is a fix for a bug that had been breaking compatible endpoints since 2.1.265BASE_URL — Third-party Anthropic-compatible endpoints behind ANTHROPIC_BASE_URL were failing every turn with HTTP 400. Upgrade before you touch your configWEBFETCH — WebFetch no longer waits forever on a server that keeps the response open. It now gives up after 300 seconds, tunable via CLAUDE_CODE_WEBFETCH_DEADLINE_MSSECRET — Secrets resolved from ${VAR} placeholders in MCP configs were being printed by /mcp and claude mcp list. Worth knowing if you share your screenCPU — A busy loop that pinned a core during long idle sessions is fixed, so that fan you could not explain may finally settle downRESUME — --continue and --resume now show the conversation right away instead of waiting on SessionStart hooks
TAG

timeouts

1 articles
Back to all tags
Related:
Claude Code1WebFetch1environment variables1unattended runs1
Claude Code/2026-09-12Intermediate

My overnight crawl never came back, and the reason was that WebFetch had no ceiling on how long it would wait

Claude Code v2.1.268 gives WebFetch a 300-second deadline. Here is how an unattended run stalls on a server that never closes its response, why CLAUDE_CODE_WEBFETCH_DEADLINE_MS=0 does not mean 'do not wait', and how I now place two separate ceilings.