{"version":"2.1.300","anchor":"pasted-text-and-the-bridge-no-longer-skip-slash-command-hand","canonical_anchor":"pasted-text-and-the-bridge-no-longer-skip-slash-command-hand","heading":"Slash text that was not typed is handled differently over the bridge","tier":"internal","area":"Bridge","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/pasted-text-and-the-bridge-no-longer-skip-slash-command-hand","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Slash text that was not typed is handled differently over the bridge\n\nFor messages arriving through the bridge, Claude Code now checks whether slash text was actually typed before handling it as a command\n\n**Unclear.** It is not clear whether slash text that was not typed now runs as a command or is sent on as plain text.\n\n**What**\n\nA slash command is a message starting with `\/`, such as `\/help`. The bridge is the connection Claude Code uses for remote sessions. For messages that arrive through the bridge, Claude Code now checks whether the slash text was typed by a person. If it was not typed, for example because it was pasted in, the check that decides how a bridge slash message is handled now gives a different result.\n\n**Why**\n\nThis matters if you use remote or bridge sessions and paste text that starts with a slash.\n\n- Area: Bridge\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}