›_ Claude Code Issues
Claude Code Issues / #75098

[DOCS] Remote Control mobile/web slash commands: docs lack v2.1.202 "Unknown command" fix note

Open 💬 0 comments Opened Jul 7, 2026 by coygeek

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/remote-control

Section/Topic

The "Limitations" section, specifically the bullet that begins:

Some commands are local-only: commands that open an interactive picker in the terminal, such as /plugin or /resume, work only from the local CLI. The following work from mobile and web:

This is the only place on the page that lists which slash commands are supported from the Remote Control mobile/web clients (currently /compact, /clear, /context, /usage, /exit, /usage-credits, /recap, /reload-plugins).

Current Documentation

The current Limitations bullet simply lists the supported commands with no historical note:

Some commands are local-only: commands that open an interactive picker in the terminal, such as /plugin or /resume, work only from the local CLI. The following work from mobile and web: Text-output commands: /compact, /clear, /context, /usage, /exit, /usage-credits, /recap, /reload-plugins mcp, from v2.1.166: returns a text summary of server status instead of opening the picker, and accepts the reconnect, enable, and disable subcommands. Unlike the local CLI, mcp reconnect without a server name reconnects every server that has failed or needs authentication. config, from v2.1.181: pass key=value to set a setting, or run it with no argument to list the keys you can set.

For comparison, other v2.1.202 fixes are documented inline as {/* min-version: 2.1.202 */}Before v2.1.202, ... notes on the same page and elsewhere — for example:

The v2.1.202 changelog entry for this fix reads:

Fixed commands sent from Remote Control (mobile/web) into an interactive session failing with "Unknown command"

This same wording — Unknown command: /<name> — matches the symptom reported on the supported-commands path: the local registry recognises the command, the fuzzy suggester echoes it back, but the remote-side dispatcher cannot execute it.

What's Wrong or Missing?

A. The Limitations bullet on the Remote Control page does not include a v2.1.202 historical note

For users reading the page, the current text reads as if every text-output command on that list has always worked from mobile/web, with the only version annotations being v2.1.166 for /mcp and v2.1.181 for /config. There is no note for the v2.1.202 fix that makes the listed commands reliably dispatch from the remote side.

The shipped behavior matches the docs (the fix landed in 2.1.202), but the docs do not say what was broken before, so anyone reading older copies of the page, comparing across versions, or triaging a regression ticket cannot tell from the docs that the previously reported Unknown command path through the remote dispatcher was specifically the v2.1.202 fix.

B. The supported-commands bullet silently changed meaning at v2.1.202

Before v2.1.202, the bullet listed commands that the docs claimed worked from mobile/web but which could fail at runtime with Unknown command: /<name> even though /usage (or any of the other listed commands) ran fine in the local terminal. The fix means that for v2.1.202 and later, the docs claim is now actually true in all listed cases. Without a min-version: 2.1.202 note on the same bullet, the historical accuracy of the page regressed silently.

Suggested Improvement

Add a min-version: 2.1.202 annotation to the Limitations bullet so the historical fix is visible next to the supported-commands list, mirroring the style already used elsewhere on the same page for the v2.1.202 attachment fix at line 19.

Specifically, update the "Some commands are local-only" bullet so that the supported-commands sub-bullets each carry (or one collective sub-bullet carries) the following note immediately after the list:

The text-output commands listed above dispatch from the remote client as expected. Before v2.1.202, commands sent from a Remote Control mobile or web client into an interactive session could fail with Unknown command: /<name> even though the same command ran fine in the local terminal. Requires Claude Code v2.1.202 or later.

Then, if the per-bullet min-version style is preferred for consistency with the v2.1.166 and v2.1.181 sub-bullets below it, attach a {/* min-version: 2.1.202 */} annotation directly to the first text-output sub-bullet:

* Text-output commands: /compact, /clear, /context, /usage, /exit, /usage-credits, /recap, /reload-plugins — from v2.1.202, these dispatch reliably from the mobile and web clients; before v2.1.202 they could fail with Unknown command: /<name> even though the local terminal executed the same command without error.

Either form makes the version boundary visible inline, mirrors the existing {/* min-version: 2.1.202 */} style used for the other v2.1.202 fixes on the same page, and preserves the cross-references to /mcp (v2.1.166) and /config (v2.1.181) that already appear below the list.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/remote-control | 261-265 | "Some commands are local-only" bullet lists the text-output commands that work from mobile/web but carries no min-version: 2.1.202 annotation, despite the v2.1.202 changelog entry fixing the underlying remote-dispatch path |

Total scope: 1 page affected.

Related v2.1.202 fixes that already have inline notes (for consistency reference):

Changelog version: v2.1.202 (July 6, 2026).

View original on GitHub ↗