You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
InternalsArea: what it touches
Bug FixesKind: in v2.1.305,
Bug FixesSection of the release
What
When a request times out, Claude Code can suggest increasing API_TIMEOUT_MS, the time limit for requests in milliseconds. That hint used to appear whenever API_TIMEOUT_MS was set in your shell. It now uses the value Claude Code actually resolved, including one set in the env section of your settings, and appears only when the value is above zero. A zero or empty value no longer brings up the hint.
Why
The hint now matches the time limit actually in use, so it shows up when you set it in settings and not when it is zero or empty.
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 sinceAnthropic's documentation has since written up API_TIMEOUT_MS, on Claude apps gateway deployment and operations.### Keep `API_TIMEOUT_MS` above the gateway's time to first byteclaude-apps-gateway-deploysee 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 API_TIMEOUT_MS, on Claude apps gateway deployment and operations.
