Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.268 ·

Advisor tool model-resolution path now also receives credentials

Model-resolution during the main loop now also receives credentials, and the advisor-tool consent call was renamed

Under the hood Internal Changes
JSON All of v2.1.268
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.268,
Internal ChangesSection of the release

Unclear It's unclear what effect passing credentials into model resolution has for the user, beyond the internal rename.

What

The internal function that resolves which model to use during the main loop, now called Jm (previously Hm), takes an added credentials argument alongside the user-specified model, agent model, and other settings. Separately, the confirmation step in the advisor-tool consent flow was renamed internally, and still logs the advisor_fable_consent event.

Why

The finding doesn't say what using credentials in model resolution changes in practice; it's an internal wiring change rather than a new user-facing behavior.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt's unclear what effect passing `credentials` into model resolution has for the user, beyond the internal rename.

See this entry in the whole of v2.1.268 →

Feedback