{"version":"2.1.323","anchor":"rate-limit-auto-open-keyed-by-limit-type-and-plugin-denied-t","canonical_anchor":"rate-limit-auto-open-keyed-by-limit-type-and-plugin-denied-t","heading":"Different usage limits each open the limit menu, and plugin-removed tools are refused","tier":"notice","area":"Usage & Limits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/rate-limit-auto-open-keyed-by-limit-type-and-plugin-denied-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Different usage limits each open the limit menu, and plugin-removed tools are refused\n\nThe automatic `\/rate-limit-options` menu now tracks each limit type separately, and tools a plugin removed are refused with a clear message\n\n**What**\n\n- `\/rate-limit-options`: Claude Code opens this menu by itself when you hit a usage limit, and it remembers which limit it already opened for. It now tells limits apart by their type as well as their reset time. Before, it went by the reset time alone.\n\n- Tools removed by a plugin: if a plugin (an add-on) removed a tool from your session, a call to that tool is now refused with the message that it is not available because a plugin removed it.\n\n**Why**\n\nHitting one kind of limit no longer stops the menu from opening for a different kind that happens to reset at the same time.\n\n- Area: Usage & Limits\n- Names: `\/rate-limit-options`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}