{"version":"2.1.223","anchor":"slash-commands-can-announce-a-default-effort-level-via-a-not","canonical_anchor":"slash-commands-can-announce-a-default-effort-level-via-a-not","heading":"Slash commands can announce a default effort level via a notice","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/slash-commands-can-announce-a-default-effort-level-via-a-not","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Slash commands can announce a default effort level via a notice\n\nSlash commands can tell you which effort level they defaulted to when you didn't specify one.\n\n**What**\n\nCommand dispatch gained two optional hooks, `onUserTypedArgs` for interactive invocations and `getDefaultEffort`, whose returned `.notice` is rendered as a notice message when the user did not type an effort explicitly.\n\n**Details**\n\n- effort resolution order for a command is now `getEffort ?? getDefaultEffort()?.value ?? effort`\n- `onUserTypedArgs` fires only for interactive invocations, not programmatic dispatch\n- the notice is shown only when no explicit effort was typed, so a user-supplied effort stays silent\n\n**Evidence**\n\n`let k = g.getDefaultEffort?.(A, n)?.notice;`\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}