{"version":"2.1.280","anchor":"model-effort-level-resolution-changed-for-usersettings-sourc","canonical_anchor":"model-effort-level-resolution-changed-for-usersettings-sourc","heading":"Effort-level and ultracode setting resolution reworked","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/model-effort-level-resolution-changed-for-usersettings-sourc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Effort-level and ultracode setting resolution reworked\n\nThe logic that figures out each model's effort level and whether ultracode is active was reworked, changing how userSettings and legacy effort settings combine.\n\n**Unclear.** What the new model check specifically verifies, and which configurations are affected in practice, is not stated in the evidence.\n\n**What**\n\n- The function that resolves the effective effort level for a model across settings sources changed how it treats a setting from the \"userSettings\" source: it's now only honored if another, non-userSettings source also matched, or a new check passes for that model. Previously any userSettings `effortLevel` was used directly.\n\n- The broader function computing per-model effort levels was rewritten to separate a top-level \"legacy user effort\" from settings-file-declared effort and to track which source sets the top-level default; when ultracode is on for the whole session it now returns a default of `xhigh` plus a per-model map, instead of the previous empty per-model map.\n\n- The check for whether ultracode mode is active (via settings or a keyword trigger) no longer performs an extra side-effect call as part of just checking the boolean; it's now a pure check.\n\n**Why**\n\nThis makes effort-level resolution more predictable, so settings-file values and legacy user settings interact consistently, and checking whether ultracode is on no longer has unrelated side effects.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}