Remote Control blocks unavailable slash commands on the new 'relay' surface, not just 'bridge', and logs which surface triggered it
What
When you use Claude Code over Remote Control and try to run a slash command that isn't available remotely, Claude Code already told you so for the 'bridge' surface. That same check now also runs for a second surface called 'relay'. Internally the single check was split into two functions, one per surface, but both feed into the same shared logic.
The telemetry and messaging behind this check now record which surface, 'bridge' or 'relay', triggered the block.
Why
This closes a gap where a slash command could be blocked as unavailable on one Remote Control surface but not the other, so the restriction is now applied consistently everywhere Remote Control is used.
Nothing has been read yet about whether the `tengu_slash_command_unavailable` gate is on or off for this site's account.