[BUG] /context rejected as "Unknown command: /context. Did you mean /context?" in Remote Control session (v2.1.201)

Open 💬 0 comments Opened Jul 5, 2026 by medicusdkfz

Environment

  • Claude Code v2.1.201, host: macOS (darwin 25.3.0), Terminal.app
  • Remote Control session opened from an iPad (Claude mobile/web UI) connected to the running local session

Steps to reproduce

  1. Start a Claude Code session in the macOS terminal.
  2. Connect to the same session from an iPad via Remote Control.
  3. In the remote UI, type /context.

Expected

Context-window usage breakdown. The Remote Control docs explicitly list /context among the text-output commands that work from mobile and web (alongside /compact, /usage, /clear, /recap): https://code.claude.com/docs/en/remote-control

Actual

Unknown command: /context. Did you mean /context?

The suggestion is character-identical to the input, so this is not a typo/Unicode issue — the fuzzy matcher clearly resolves the string, but the command is not executable in the remote context.

Additional observations

  • /usage works fine from the same remote session (so remote slash-command dispatch works in general).
  • /context works fine in the local macOS terminal for the very same session.
  • Practical impact: there is currently no way to see remaining context-window usage from the mobile remote UI — the status line (e.g. 170k/1000k — 17%) exists only in the local TUI, and /usage shows subscription quota, not context fill.

Looks like the remote command registry is missing /context while the suggestion index still contains it.

View original on GitHub ↗