{"version":"2.1.224","anchor":"rate-limit-headers-from-before-a-login-change-are-discarded","canonical_anchor":"rate-limit-headers-from-before-a-login-change-are-discarded","heading":"Rate-limit headers from before a login change are discarded","tier":"notice","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/rate-limit-headers-from-before-a-login-change-are-discarded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Rate-limit headers from before a login change are discarded\n\nRate-limit info from before you logged in or out can no longer overwrite fresh state.\n\n**What**\n\nRate-limit tracking now carries a version marker that increments when login state resets, so a response that was already in flight when you logged in or out cannot overwrite the fresh state. The reset also returns status to allowed and clears overage flags.\n\n**Evidence**\n\n`anthropic-ratelimit-unified-grace-status`\n\n- Area: Rate Limits\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}