{"version":"2.1.268","anchor":"advisor-tool-model-resolution-path-now-also-receives-creden","canonical_anchor":"advisor-tool-model-resolution-path-now-also-receives-creden","heading":"Advisor tool model-resolution path now also receives credentials","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/advisor-tool-model-resolution-path-now-also-receives-creden","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Advisor tool model-resolution path now also receives `credentials`\n\nModel-resolution during the main loop now also receives credentials, and the advisor-tool consent call was renamed\n\n**Unclear.** It's unclear what effect passing `credentials` into model resolution has for the user, beyond the internal rename.\n\n**What**\n\nThe 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.\n\n**Why**\n\nThe 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.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}