Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

rateLimitFailFastEnabled

setting never mined JSON

A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

Auto mode's remote config gains rateLimitFailFastEnabled, which keeps retry waits within a request's deadline

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.281.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 126on this box, as of v2.1.283
Written about v2.1.281 first named in a changelog, 23 Sep 2026

In the changelogs

4

Releases whose published page names rateLimitFailFastEnabled.

  1. v2.1.282
    A deadline-limited request can cap how long it waits on rate limits

    One time-limited API request can now pass its remaining time as a limit on rate-limit waits, when a setting is turned on

    named in this entry, found in this entry's text

  2. v2.1.281
    New rateLimitFailFastEnabled field in tengu_auto_mode_config

    Auto mode's remote config gains rateLimitFailFastEnabled, which keeps retry waits within a request's deadline

    found in this entry's text

  3. v2.1.281
    Auto mode: stage-2 classifier rate-limit errors carry the retry-after delay

    In auto mode, a rate-limited safety check now tells Claude how long to wait instead of calling the error transient

    found in this entry's text

  4. v2.1.281
    Side queries with a deadline fail fast on long Retry-After, behind auto-mode config

    Deadline-bound side queries can now give up at once when the API asks for a wait longer than the time left

    found in this entry's text

First cited

1

The earliest release whose published evidence quoted rateLimitFailFastEnabled was v2.1.281, 23 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.28123 Sep 2026rateLimitFailFastEnabled

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.

Feedback