{"version":"2.1.277","anchor":"rate-limit-usage-response-strips-limits-when-status-is-se","canonical_anchor":"rate-limit-usage-response-strips-limits-when-status-is-se","heading":"Rate-limit usage response strips 'limits' when status is 'seeded'","tier":"notice","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/rate-limit-usage-response-strips-limits-when-status-is-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Rate-limit usage response strips 'limits' when status is 'seeded'\n\nRate-limit usage responses no longer include per-limit detail when status is 'seeded'\n\n**Unclear.** What the 'seeded' status specifically represents, and why per-limit detail is excluded for it, is not stated\n\n**What**\n\nWhen the rate-limit status returned is `seeded`, Claude Code now removes the `limits` field before building the rate-limit usage object it returns, so a seeded response no longer includes the detailed per-limit breakdown.\n\n**Why**\n\nThis changes what information is available when rate-limit usage is in the 'seeded' state; per-limit detail won't show up for that case anymore.\n\n- Area: Rate Limits\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}