{"version":"2.1.295","anchor":"rate-limit-warning-can-include-overageenabled","canonical_anchor":"resume-dialog-gets-a-trigger-tag-plugin-enabled-check-chang","heading":"Rate-limit warnings can know whether extra usage is on; small resume and plugin changes","tier":"notice","area":"Usage & Limits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/rate-limit-warning-can-include-overageenabled","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Rate-limit warnings can know whether extra usage is on; small resume and plugin changes\n\nThe usage-limit warning can now take an `overageEnabled` value, alongside a resume dialog trigger tag and a changed plugin enabled check\n\n**Unclear.** When this applies and how the warning wording changes is not known.\n\n**What**\n\nThe warning Claude Code shows when you are nearing a usage limit can now take into account whether extra usage is turned on for your account.\n\n- The rate-limit message helper accepts a new `overageEnabled` option.\n\n- For an `allowed_warning` status on a limit type that is not about overage, the options now carry `overageEnabled`, taken from `hasExtraUsageEnabled`. This only happens when a further check passes, and that check was not identified. Before, only `includeOverageInUse` and `unifiedWindows` were passed.\n\nThe finding also noted two small, separate changes in this release.\n\n- A dialog on the path that resumes an earlier session now passes `trigger: \"resume\"`.\n\n- The check that decides which plugins are enabled now tests each plugin on its own, instead of using a single shared test.\n\n**Why**\n\nIf your account has extra usage enabled, the usage-limit warning text may now differ from what you saw before.\n\n- Area: Usage & Limits\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}