{"version":"2.1.282","anchor":"rate-limit-fail-fast-budget-for-a-deadline-bound-api-call","canonical_anchor":"rate-limit-fail-fast-budget-for-a-deadline-bound-api-call","heading":"A deadline-limited request can cap how long it waits on rate limits","tier":"soon","area":"Rate Limits","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/rate-limit-fail-fast-budget-for-a-deadline-bound-api-call","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### A deadline-limited request can cap how long it waits on rate limits\n\nOne time-limited API request can now pass its remaining time as a limit on rate-limit waits, when a setting is turned on\n\n**Unclear.** It is unclear which request this applies to and which configuration supplies `rateLimitFailFastEnabled`.\n\n**What**\n\nFor an API request that has to finish before a deadline, Claude Code can now pass along how much time is left as a budget for waiting after a rate limit (a temporary \"slow down\" answer from the server). This happens only when a configuration value named `rateLimitFailFastEnabled` is exactly true, so it is off unless that value is supplied.\n\n**Why**\n\nIn practice, when it is turned on, a request that hits a rate limit should give up rather than wait past its deadline.\n\n- Flag `tengu_auto_mode_config`: Not enough to say (read for one account on one subscription tier against v2.1.282; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Rate Limits\n- Names: `rateLimitFailFastEnabled`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}