{"version":"2.1.287","anchor":"slash-command-skip-check-for-bridge-messages","canonical_anchor":"slash-command-skip-check-for-bridge-messages","heading":"Reworked check for when slash commands are not sent to Claude","tier":"internal","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/slash-command-skip-check-for-bridge-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Reworked check for when slash commands are not sent to Claude\n\nA message starting with \/ is not sent to the model when slash commands are set to be skipped, or when it comes over a bridge and fails a check\n\n**Unclear.** This may only reorganise existing behaviour, and it is not clear what the further check for bridge messages tests.\n\n**What**\n\nA slash command is a message starting with `\/`, such as a built-in command. Claude Code decides whether such a message is sent to the model or not. That decision now sits in its own check. A message starting with `\/` is not sent to the model when:\n\n- slash commands are set to be skipped, or\n\n- it arrives through a bridge connection and fails a further check.\n\n**Why**\n\nSlash commands sent from a remote or bridge connection may be handled differently from ones typed directly.\n\n- Area: Slash Commands\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}