{"version":"2.1.239","anchor":"per-model-effort-level-in-settings-behind-a-gate","canonical_anchor":"per-model-effort-level-in-settings-behind-a-gate","heading":"Per-model effort level in settings, behind a gate","tier":"soon","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/per-model-effort-level-in-settings-behind-a-gate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Per-model effort level in settings, behind a gate\n\nYou could set an effort level per model in settings, but the lookup is gated off.\n\n**What**\n\nAny settings layer can set `modelSettings.<model>.effortLevel`, which overrides the top-level `effortLevel` for that one model, with model ids normalised before lookup. Saving effort to user settings writes both the top-level key and the per-model entry. The lookup is gated on `tengu_russet_plover`, which falls back to false, so absent a server value the per-model table stays empty and effort behaves exactly as before.\n\n**Details**\n\n- Session effort is now a tagged value: an explicit level, the default, or inherited.\n\n**Evidence**\n\n`tengu_russet_plover`\n\n- Flag `tengu_russet_plover`: Off in both readings (read for one account on one subscription tier against v2.1.239; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Settings\n- Names: `effortLevel`, `modelSettings`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}