{"version":"2.1.239","anchor":"a-low-priority-choice-is-wired-into-the-usage-limit-menu","canonical_anchor":"a-low-priority-choice-is-wired-into-the-usage-limit-menu","heading":"A low-priority choice is wired into the usage-limit menu","tier":"soon","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/a-low-priority-choice-is-wired-into-the-usage-limit-menu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### A low-priority choice is wired into the usage-limit menu\n\nThe usage-limit menu has a lower-priority choice wired in alongside login and auto-resume.\n\n**What**\n\nThe internal map of what each usage-limit menu choice does now lists `low-priority` as an action, next to login, logout, mock limits and OAuth refresh, and the menu pushes that option conditionally. It counts as a plain action rather than an upgrade, so it is grouped with cancel and auto-resume instead of the upgrade, team and extra-usage choices.\n\n**Details**\n\n- What makes the menu entry appear at runtime is decided elsewhere in the limits flow.\n\n**Evidence**\n\n`\"low-priority\": \"action\"`\n\n- Area: Usage & Limits\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}