Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.248 Home All releases olderv2.1.247 v2.1.250newer
Claude Code v2.1.248

Usage-limit messages stop telling you to run /usage-credits when it will not help

You'll notice
Useful3 Signal2
Usage & Limits

Limit messages stop pointing at /usage-credits when that flow isn't available to you.

/usage-credits
What

Limit and rate-limit messages now pick their wording based on whether the credits flow is actually available to you.

Details
  • Admin-limit text is either " · run /usage-credits to ask your admin for a higher limit" or the plain " · 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.
  • The spend-cap branch chooses between " · run /usage-credits to raise it, or visit claude.ai/admin-settings/usage" and " · visit claude.ai/admin-settings/usage to raise it".
  • 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.
  • The choice comes from an internal predicate whose input is not visible in the build.
Evidence

· ask your admin for a higher limit, run /model to switch to standard context

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.248 →