{"version":"2.1.309","anchor":"slash-commands-from-relay-participants-are-refused-with-a-di","canonical_anchor":"slash-commands-from-relay-participants-are-refused-with-a-di","heading":"Relay participants get their own message when a command is refused","tier":"notice","area":"Relay","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/slash-commands-from-relay-participants-are-refused-with-a-di","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Relay participants get their own message when a command is refused\n\nSlash commands from relay participants are now refused with a message saying they aren't available to a relay participant\n\n**Unclear.** Which slash commands are refused to relay participants is not stated.\n\n**What**\n\nClaude Code now checks slash commands sent by relay participants, people taking part in a session through a relay, and refuses some of them. The message reads that the command isn't available to a relay participant. Commands sent over Remote Control keep their own wording saying they aren't available over Remote Control.\n\nA command that gets queued again is now marked so it is not treated as a slash command a second time.\n\n**Why**\n\nThis limits what relay participants can run in a session.\n\n- Area: Relay\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}