{"version":"2.1.304","anchor":"misc-ui-custom-api-key-prompt-disable-slash-commands-tex","canonical_anchor":"misc-ui-custom-api-key-prompt-disable-slash-commands-tex","heading":"Help text for --disable-slash-commands now mentions commands too","tier":"notice","area":"CLI","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/misc-ui-custom-api-key-prompt-disable-slash-commands-tex","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Help text for `--disable-slash-commands` now mentions commands too\n\n`--disable-slash-commands` is now described as disabling all skills and commands, and plugin publishing no longer promises a scan\n\n**What**\n\nSeveral small wording and display changes:\n\n- `--disable-slash-commands` is now described as \"Disable all skills and commands\" instead of \"Disable all skills\".\n\n- The instructions Claude gets for publishing a plugin now say that whether claude.ai scans the plugin depends on your organisation.\n\n- The dialog asking you to approve a custom API key indents the key line, and approving now runs an extra step.\n\n- Detection of PowerShell can now stop early in some cases.\n\n**Why**\n\nThe help text now matches what the flag does, and Claude no longer tells you a published plugin is always scanned when that is up to your organisation.\n\n- Area: CLI\n- Names: `--disable-slash-commands`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}