{"version":"2.1.300","anchor":"slash-commands-run-immediately-now-record-to-history-as-type","canonical_anchor":"slash-commands-run-immediately-now-record-to-history-as-type","heading":"Slash commands that run at once are saved to your input history once","tier":"notice","area":"Prompt History","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/slash-commands-run-immediately-now-record-to-history-as-type","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Slash commands that run at once are saved to your input history once\n\nSlash commands that run straight away are now saved to input history once, as `\/name` plus arguments when what ran differs from what you typed\n\n**What**\n\nSlash commands are the commands you type starting with `\/`. Claude Code keeps a history of what you enter, which you can step back through with the up arrow. Commands that run immediately on your machine now save their history entry once, through a single shared step.\n\nIf the saved entry would not match what you typed, Claude Code saves it as `\/name` followed by the arguments. A slash command that has to be checked before it runs is saved once that check finishes.\n\n**Why**\n\nThis affects what you see when you press the up arrow to bring back an earlier slash command.\n\n- Area: Prompt History\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}