Desktop (Code tab): /remote-control falls through to the model instead of being executed by the client

Resolved 💬 2 comments Opened May 28, 2026 by portax4 Closed Jun 1, 2026

Environment

  • Claude Desktop 1.9659.1.0 (MSIX / Microsoft Store, Windows 11 x64)
  • Claude Code engine 2.1.126
  • Auth: claude.ai OAuth (Max plan)

Repro

  1. In the Desktop app Code tab, open/continue a session
  2. Type /remote-control — it appears in autocomplete with the tooltip "View and control this session from claude.ai/code"
  3. Select it and submit

Expected
Client connects the session to claude.ai/code and shows a session URL / QR code.

Actual
The command is sent to the model as a prompt (renders as a blue /remote-control chip followed by an assistant turn). No connection, no URL/QR. The assistant has no remote-control capability, so nothing happens.

Notes

  • This used to work in the Desktop app previously; it appears to have regressed.
  • CLI works fine (claude remote-control, or /remote-control inside a terminal claude session).
  • So the command is registered in the Code tab's autocomplete but is not handled by the client there — it falls through to the agent.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗