{"version":"2.1.309","anchor":"slash-command-dispatch-gets-a-pre-run-interceptor","canonical_anchor":"slash-command-dispatch-gets-a-pre-run-interceptor","heading":"Slash commands can now be intercepted before they run","tier":"internal","area":"Slash Commands","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/slash-command-dispatch-gets-a-pre-run-interceptor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Slash commands can now be intercepted before they run\n\nCode that runs slash commands can now pass a check that sees each command first and can return its own result instead\n\n**What**\n\nSlash commands are commands you type starting with `\/`. The part of Claude Code that runs them can now be given an extra check that sees each command, its name and its arguments before it runs. Commands handled entirely inside Claude Code are not passed to it. If the check returns a result, that result is shown as the command's output and the command itself does not run.\n\nBefore, Claude Code found and ran slash commands directly, with nothing in between.\n\n**Why**\n\nA program that hosts Claude Code could use this to answer or stop a slash command before it runs.\n\n- Area: Slash Commands\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}