{"version":"2.1.285","anchor":"api-timeout-ms-is-now-capped","canonical_anchor":"api-timeout-ms-is-now-capped","heading":"Very large API_TIMEOUT_MS values are now capped","tier":"notice","area":"API","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/api-timeout-ms-is-now-capped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Very large API_TIMEOUT_MS values are now capped\n\nA value you set for `API_TIMEOUT_MS` is now held to a maximum instead of being used however large it is\n\n**Unclear.** The maximum value is not stated.\n\n**What**\n\n`API_TIMEOUT_MS` is an environment variable that sets how long, in milliseconds, Claude Code waits for a request to the model. A value you set is now reduced to a fixed maximum when it is larger. Before, any value was used as given.\n\n**Why**\n\nVery large timeouts are no longer used as written. If you set a huge value, Claude Code will wait at most the maximum.\n\n- Area: API\n- Names: `API_TIMEOUT_MS`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}