{"version":"2.1.265","anchor":"slash-commands-can-now-supply-custom-argument-autocompletion","canonical_anchor":"slash-commands-can-now-supply-custom-argument-autocompletion","heading":"Slash commands and skills gain menuDescription, policyGate, and custom argument autocompletion","tier":"use","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/slash-commands-can-now-supply-custom-argument-autocompletion","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Slash commands and skills gain menuDescription, policyGate, and custom argument autocompletion\n\nCommands and skills can now define a shorter menu description, a policy-based visibility gate, and custom argument autocomplete\n\n**What**\n\n- Commands and skills can now define a `getArgumentCompletions` callback; the prompt input calls this while typing to generate custom suggestions for a command's arguments.\n\n- Command\/skill definitions gained a `menuDescription` field: a shorter description shown in menu\/listing UI, separate from the full description.\n\n- Command\/skill definitions gained a `policyGate` field: a policy object with a `.policy` check that can hide or disable a command.\n\n- Internally, `policyGate` is now set up as a lazy getter during registration (rather than a plain assigned property), and `getArgumentCompletions` is passed through registration alongside it.\n\n**Why** These fields give command and skill authors more control over how their commands appear and behave in menus: a concise label for tight UI space, a way to restrict visibility based on policy, and live, tailored argument suggestions instead of generic ones.\n\n- Area: Slash Commands\n- Names: `getArgumentCompletions`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}