{"version":"2.1.305","anchor":"api-timeout-ms-error-hint-now-read-from-the-settings-env-sh","canonical_anchor":"api-timeout-ms-error-hint-now-read-from-the-settings-env-sh","heading":"Timeout hint now notices API_TIMEOUT_MS set in settings","tier":"notice","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/api-timeout-ms-error-hint-now-read-from-the-settings-env-sh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Timeout hint now notices `API_TIMEOUT_MS` set in settings\n\nThe hint to raise API_TIMEOUT_MS after a timeout now uses the value from settings too, and only appears when it is above zero\n\n**What**\n\nWhen 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.\n\n**Why**\n\nThe 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.\n\n- Area: Internals\n- Names: `API_TIMEOUT_MS`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}