{"version":"2.1.248","anchor":"usage-limit-messages-stop-telling-you-to-run-usage-credits-w","canonical_anchor":"usage-limit-messages-stop-telling-you-to-run-usage-credits-w","heading":"Usage-limit messages stop telling you to run \/usage-credits when it will not help","tier":"notice","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/usage-limit-messages-stop-telling-you-to-run-usage-credits-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Usage-limit messages stop telling you to run \/usage-credits when it will not help\n\nLimit messages stop pointing at \/usage-credits when that flow isn't available to you.\n\n**What**\n\nLimit and rate-limit messages now pick their wording based on whether the credits flow is actually available to you.\n\n**Details**\n\n- Admin-limit text is either \" \u00b7 run \/usage-credits to ask your admin for a higher limit\" or the plain \" \u00b7 ask your admin for a higher limit\"; the same helper now supplies this for the member-level-disabled and group-zero-credit-limit messages, which used to hard-code the command.\n- The spend-cap branch chooses between \" \u00b7 run \/usage-credits to raise it, or visit claude.ai\/admin-settings\/usage\" and \" \u00b7 visit claude.ai\/admin-settings\/usage to raise it\".\n- The 1M-context 429 hint now has three branches: the web console link, the existing \/usage-credits plus \/model wording, and a new fallback mentioning only `run \/model to switch to standard context`.\n- The choice comes from an internal predicate whose input is not visible in the build.\n\n**Evidence**\n\n` \u00b7 ask your admin for a higher limit`, `run \/model to switch to standard context`\n\n- Area: Usage & Limits\n- Names: `\/usage-credits`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}