{"version":"2.1.301","anchor":"slash-commands-can-now-trigger-a-model-turn-after-running-o","canonical_anchor":"slash-commands-can-now-trigger-a-model-turn-after-running-o","heading":"Slash commands can now hand Claude a follow-up prompt after they run","tier":"notice","area":"Slash Commands","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/slash-commands-can-now-trigger-a-model-turn-after-running-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Slash commands can now hand Claude a follow-up prompt after they run\n\nA slash command can now pass along a follow-up prompt that makes Claude respond after the command finishes, instead of always stopping\n\n**Unclear.** No command is named that uses this, so it may not affect any command yet.\n\n**What**\n\nSlash commands are the commands you type starting with `\/`. Some of them run entirely inside Claude Code without asking the model anything. Before this release, those commands never sent anything to the model afterwards.\n\nThese commands can now include a follow-up prompt. When one does, the prompt is added to the conversation as a hidden note and Claude is asked to respond, so the command flows straight into a reply from the model.\n\n**Why**\n\nThis gives commands a way to continue into a model response on their own, rather than stopping after they run.\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}