{"version":"2.1.281","anchor":"429-and-overload-messages-drop-the-model-hint-in-some-non-i","canonical_anchor":"429-and-overload-messages-drop-the-model-hint-in-some-non-i","heading":"429 and overload messages drop the \/model hint in some non-interactive sessions","tier":"notice","area":"Models","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/429-and-overload-messages-drop-the-model-hint-in-some-non-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### 429 and overload messages drop the \/model hint in some non-interactive sessions\n\nSome non-interactive sessions get high-load errors without the \/model hint, and 429 errors report their message more reliably\n\n**Unclear.** The finding does not say exactly which sessions get the shorter wording, beyond some non-interactive ones.\n\n**What**\n\nWhen Opus or Fable is under heavy load, the error in some sessions now uses a shorter wording, such as \"Opus is experiencing high load. Switch to Sonnet.\", and leaves out the hint to use `\/model`. The same condition also hides slash-command hints elsewhere. Slash commands are commands typed with a leading `\/`.\n\nTwo changes affect \"429\" errors, which the server sends when too many requests arrive or a limit is reached:\n\n- When the error body is not in JSON format, Claude Code now takes the message from the error itself\n\n- When extra usage beyond your limit is turned off, that message now starts with \"Request rejected (429)\"\n\n**Why**\n\nIn sessions where you cannot type a slash command, the error no longer suggests one you cannot use. 429 errors also give a more readable reason.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 3\/5"}