{"version":"2.1.269","anchor":"rate-limit-reporting-emits-an-explicit-empty-model-scoped-ar","canonical_anchor":"rate-limit-reporting-emits-an-explicit-empty-model-scoped-ar","heading":"Rate-limit reporting emits an explicit empty model_scoped array in a new case","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/rate-limit-reporting-emits-an-explicit-empty-model-scoped-ar","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Rate-limit reporting emits an explicit empty model_scoped array in a new case\n\nRate-limit usage reports can now explicitly show an empty per-model breakdown instead of just omitting it\n\n**What**\n\nWhen Claude Code reports rate-limit usage information, the per-model breakdown (`model_scoped`) can now come back in three different ways: a real list of per-model entries, left out entirely, or an explicit empty array. The empty array case happens when overall usage totals for the five-hour and seven-day windows exist, but per-model limit data isn't usable or available.\n\n**Why**\n\nThis lets tools reading usage data tell the difference between \"no per-model data was requested\" and \"per-model data was requested but none was available,\" which avoids ambiguity when interpreting rate-limit reports.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}