{"version":"2.1.296","anchor":"stacked-slash-command-expansion-error-check-broadened","canonical_anchor":"stacked-slash-command-expansion-error-check-broadened","heading":"Some errors while expanding stacked slash commands are no longer swallowed","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/stacked-slash-command-expansion-error-check-broadened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Some errors while expanding stacked slash commands are no longer swallowed\n\nSome errors raised while expanding stacked slash commands now stop the expansion instead of being logged and ignored\n\n**Unclear.** Exactly which kinds of error now stop the expansion is not confirmed.\n\n**What**\n\nSlash commands are the commands you type starting with `\/`. When Claude Code expands several of them that are stacked together, it decides which errors stop the expansion and which ones it only logs before carrying on.\n\nThat decision is made differently now. The old check tested a different value from the error it had actually caught, so errors that should have stopped the expansion could be logged and ignored instead. The check now looks at the caught error itself, so errors such as an interruption are expected to stop the expansion rather than be logged.\n\n**Why**\n\nThis can change what happens when you interrupt Claude Code while it is expanding slash commands. The interruption is more likely to take effect instead of being quietly recorded.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}