{"version":"2.1.277","anchor":"effort-level-command-validation-gains-a-dedicated-error-mess","canonical_anchor":"effort-level-command-validation-gains-a-dedicated-error-mess","heading":"update_settings can now validate and target userSettings.effortLevel","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/effort-level-command-validation-gains-a-dedicated-error-mess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### update_settings can now validate and target userSettings.effortLevel\n\nThe update_settings tool now accepts more setting sources, including a validated effortLevel under userSettings\n\n**What**\n\nThe `update_settings` tool previously only allowed writing to `localSettings`. It now accepts other recognized setting sources as well, each with its own set of allowed keys.\n\nWhen the source is `userSettings` and the key being set is `effortLevel`, the tool now validates that the value is one of the known, valid effort levels. If it isn't, the call fails with a new dedicated error message that lists the valid effort levels.\n\n**Why**\n\nThis prevents `update_settings` from silently accepting an invalid effort level and gives a clear, specific error message pointing to the valid options instead of a generic failure.\n\n- Area: Settings\n- Names: `effortLevel`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}