{"version":"2.1.267","anchor":"rate-limit-tracking-gains-a-locally-remembered-window-fallba","canonical_anchor":"rate-limit-tracking-gains-a-locally-remembered-window-fallba","heading":"Rate-limit tracking gains a locally-remembered-window fallback, on by default","tier":"notice","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/rate-limit-tracking-gains-a-locally-remembered-window-fallba","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Rate-limit tracking gains a locally-remembered-window fallback, on by default\n\nClaude Code can now show a rate-limit status from recently-remembered windows when a fresh server reading isn't available\n\n**Unclear.** The `tengu_sharded_moonbeam` gate controlling this hasn't been read for this site's account, so whether it's active here is unknown.\n\n**What**\n\nClaude Code tracks how close you are to hitting rate limits (caps on how much you can use the service in a given period). It now also keeps a rolling local record of recently-seen rate-limit windows, and can use that record to fill in the displayed status when a fresh reading from the server isn't available at that moment.\n\n**Why**\n\nThis should make the rate-limit indicator more reliable, avoiding gaps or blank states when a fresh server reading is momentarily missing.\n\n- Flag `tengu_sharded_moonbeam`: Not enough to say (read for one account on one subscription tier against v2.1.267; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: Rate Limits\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}