Source Intelligence
Follow Discord

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.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Auto-mode setup picks its own model and retries on a fallback

You'll notice
Useful3 Signal3
Auto Mode

Auto-mode setup picks its own scan model, retries a fallback, and names the failure.

What

The setup scan no longer takes a model from its caller; it resolves one from the auto-mode configuration. If none resolves, it fails with the new code no_model and tells you "No model is available for the scan in this session’s auto-mode configuration." If the call fails outright, it now retries once on a fallback model.

Details
  • The retry logs "auto-mode-setup propose: primary model failed; retrying on fallback" and only happens for api_failed results that were not aborted.
  • A successful retry is recorded as outcome model_fell_back on the auto_mode_setup_propose event; the missing-model case is recorded as no_model.
Evidence

auto-mode-setup propose: primary model failed; retrying on fallback, No model is available for the scan in this session’s auto-mode configuration.

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.232 →