Slash commands typed from mobile Remote Control fall through to the model as plain text instead of executing
Environment:
- Claude Code via native installer (
~/.local/bin/claude) - Platform: macOS (Darwin 25.5.0)
- Remote Control enabled on a local CLI session, driven from the Claude mobile app
Summary:
When a session has Remote Control active and is driven from the Claude mobile app, typing a built-in slash command like /context does not execute the command. Instead the text is forwarded to the model as an ordinary prompt, and the model replies conversationally. The command never runs.
Steps to reproduce:
- Start a local CLI session and run
/remote-control(or/rc) to enable Remote Control. - Open that session from the Claude mobile app.
- From mobile, type
/context.
Expected:
The /context context-usage breakdown renders (same as running /context locally in the terminal).
Actual:/context is treated as plain prompt text and sent to the model, which responds with a normal conversational answer. The slash command is never intercepted or executed.
Notes / suspected cause:
The local CLI slash-command parser does not appear to intercept commands arriving over the Remote Control channel — input from remote clients bypasses command parsing and goes straight to the model. /context renders a terminal-UI overlay, so it may simply not be in the set of commands forwarded/supported over Remote Control. Either way, the failure is silent: there is no "command not supported remotely" message, so it looks like the command was ignored. If some commands are intentionally unsupported over RC, surfacing an explicit "not available in Remote Control" notice would be clearer than silently routing to the model.
Impact:
Any TUI/overlay slash command (/context, and likely similar) is effectively unusable from mobile Remote Control, with no feedback explaining why.