Under the hood
Model-resolution during the main loop now also receives credentials, and the advisor-tool consent call was renamed
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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It's unclear what effect passing `credentials` into model resolution has for the user, beyond the internal rename.