{"version":"2.1.240","anchor":"saving-a-default-effort-level-can-now-scope-it-to-one-model","canonical_anchor":"saving-a-default-effort-level-can-now-scope-it-to-one-model","heading":"Saving a default effort level can now scope it to one model","tier":"soon","area":"Effort Levels","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.240\/e\/saving-a-default-effort-level-can-now-scope-it-to-one-model","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.240","markdown":"### Saving a default effort level can now scope it to one model\n\nYour saved default effort could apply per model instead of everywhere, but that is off.\n\n**What**\n\nPreviously, saving a default effort wrote both a global setting and a per-model one. With the `tengu_russet_plover` gate on, it now writes only the per-model entry, so the default applies to the model you are using rather than everything. With the gate off, which is the built-in default, it writes only the global setting.\n\n**Details**\n\n- The gate is remote, `tengu_russet_plover`, fallback off.\n- Model names that would collide with built-in JavaScript object property names also fall back to the global-only write.\n\n**Evidence**\n\n`{ effortLevel: t, modelSettings: { [r]: { effortLevel: t } } }`\n\n- Flag `tengu_russet_plover`: Off in both readings (read for one account on one subscription tier against v2.1.240; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Effort Levels\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}