{"version":"2.1.305","anchor":"request-timeout-now-computed-from-the-request-body","canonical_anchor":"request-timeout-now-computed-from-the-request-body","heading":"Request time limits can now depend on the request's contents","tier":"notice","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/request-timeout-now-computed-from-the-request-body","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Request time limits can now depend on the request's contents\n\nTwo of Claude Code's network request paths now work out their time limit from the request body, and clear the right timer afterwards\n\n**Unclear.** How the time limit varies with the request body is not stated.\n\n**What**\n\nIn two places where Claude Code makes network requests, the time limit used to be a fixed value. It is now worked out from the body of the request, so it can differ from one request to another. The timer that stops a request now also clears the correct timer. The general client time limit defaults to 600,000 ms (ten minutes), and a zero or negative value falls back to a built-in default.\n\n**Why**\n\nLarger requests may get more time, which could cut down on timeouts that are not real failures.\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}