[DOCS] Remote Control docs missing mobile/web command support details

Status Fixed / completed
Maintainer reply None cached
Activity 4 comments · opened Apr 16, 2026 · closed Jun 23, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

Remote Control command support from claude.ai/code and Claude mobile app clients

Current Documentation

The Remote Control page currently says:

* Work from both surfaces at once: the conversation stays in sync across all connected devices, so you can send messages from your terminal, browser, and phone interchangeably

and:

Unlike Claude Code on the web, which runs on cloud infrastructure, Remote Control sessions run directly on your machine and interact with your local filesystem. The web and mobile interfaces are just a window into that local session.

The cloud-session docs also include a command-availability table:

| /compact | Yes | Summarizes the conversation to free up context. Accepts optional focus instructions like /compact keep the test output | | /context | Yes | Shows what's currently in the context window | | /clear | No | Start a new session from the sidebar instead |

The commands reference lists /context, /exit, and /reload-plugins generically, but does not say that these commands work from Remote Control mobile/web clients. I could not find any current documentation for /autocompact as a Remote Control client command.

What's Wrong or Missing?

Changelog v2.1.110 says /autocompact, /context, /exit, and /reload-plugins now work from Remote Control (mobile/web) clients, but the Remote Control docs do not document that command support.

As written, the docs explain that Remote Control sessions can be used from the browser and mobile app, but they do not tell users which slash commands are available there or call out these newly supported commands. Users looking for compatibility guidance are likely to check the existing cloud-session command table, which is specific to cloud sessions rather than Remote Control.

Suggested Improvement

Add a short "Supported commands from Remote Control clients" subsection to the Remote Control page.

Include a compact table for the v2.1.110 change, for example:

| Command | Works from Remote Control mobile/web clients | Notes |
|------|------|------|
| /autocompact | Yes | Explain what it does when invoked remotely |
| /context | Yes | Shows current context usage from the remote client |
| /exit | Yes | Clarify whether it exits or archives the Remote Control session |
| /reload-plugins | Yes | Clarify that it reloads plugins on the local host session |

It would also help to add a brief note or cross-link from the commands reference so users know that command availability can differ between local CLI, cloud sessions, and Remote Control clients.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/remote-control | Primary page for using Claude Code from browser/mobile via Remote Control |
| https://code.claude.com/docs/en/claude-code-on-the-web | Already has a command-availability table for cloud sessions, which users may incorrectly treat as the remote-session reference |
| https://code.claude.com/docs/en/commands | Reference page for /context, /exit, and /reload-plugins; currently lacks Remote Control client availability notes |

Total scope: 3 pages affected

Source: Changelog v2.1.110

Changelog entry: /autocompact, /context, /exit, and /reload-plugins now work from Remote Control (mobile/web) clients

View original on GitHub ↗

4 Comments

coygeek · 5 months ago

Just checked the current docs again. This issue is not fully resolved yet.

coygeek · 4 months ago

Still relevant as of 2026-05-28. I checked the current docs and this documentation gap still appears unresolved.

coygeek · 3 months ago

Issue #48859 Verification

Title: [DOCS] Remote Control docs missing mobile/web command support details
Issue Date: 2026-04-16
Verification Date: 2026-06-23
Status: RESOLVED

---

Issue Summary

This issue reports that the Remote Control documentation at https://code.claude.com/docs/en/remote-control does not document which slash commands work from Remote Control (mobile/web) clients. The reporter cites changelog v2.1.110 as having added /autocompact, /context, /exit, and /reload-plugins to the list of commands available from Remote Control clients, and asks for a "Supported commands from Remote Control clients" subsection with a compact table.

---

Verification Results

Claim 1: Changelog v2.1.110 added /context, /exit, and /reload-plugins for Remote Control clients

Status: RESOLVED

Evidence: At https://code.claude.com/docs/en/changelog, line 1500:

/context, /exit, and /reload-plugins now work from Remote Control (mobile/web) clients

This matches the changelog claim for these three commands. The Remote Control documentation now lists all three as text-output commands available from mobile and web clients at https://code.claude.com/docs/en/remote-control, lines 201-202:

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

Verdict: All three commands from the v2.1.110 changelog are documented in the Remote Control page as available from mobile and web clients.

---

Claim 2: Changelog v2.1.110 added /autocompact for Remote Control clients

Status: RESOLVED

Evidence: The v2.1.110 changelog entry at https://code.claude.com/docs/en/changelog, lines 1491-1525, does not mention /autocompact at all. The full list of additions and changes in v2.1.110 includes only /context, /exit, and /reload-plugins (line 1500) as Remote Control client commands. There is also no /autocompact user-invoked slash command documented anywhere in docs/code.claude.com/ — the term "autocompact" appears only in the context of automatic compaction behavior and the CLAUDE_AUTOCOMPACT_PCT_OVERRIDE and CLAUDE_CODE_AUTO_COMPACT_WINDOW environment variables.

Verdict: The reporter's reference to /autocompact in v2.1.110 appears to be a misreading of the changelog. The command was never added in v2.1.110, and the documentation correctly omits it.

---

Claim 3: Remote Control page lacks a "Supported commands from Remote Control clients" subsection

Status: RESOLVED

Evidence: The Remote Control page at https://code.claude.com/docs/en/remote-control, lines 195-204, contains a "Limitations" section that documents exactly which commands work from mobile and web clients. It distinguishes between commands that are local-only (e.g., /plugin, /resume, which open interactive pickers) and a list of text-output commands that work remotely, followed by version-specific notes for /mcp (from v2.1.166) and /config (from v2.1.181). This serves the same purpose as the reporter's suggested "Supported commands from Remote Control clients" subsection, and is presented in a clear, scannable bullet-list format under "Limitations".

Verdict: The Remote Control page now contains an explicit list of commands that work from mobile and web clients. The format differs from the suggested compact table but conveys the same information.

---

Claim 4: Commands reference page lacks Remote Control availability notes for these commands

Status: PARTIALLY RESOLVED

Evidence: The commands reference at https://code.claude.com/docs/en/commands documents /context (line 64), /exit (line 73), and /reload-plugins (line 107) but does not include Remote Control client availability notes for any of them. By contrast, /config (line 63) does mention Remote Control compatibility (The key=value form also works in non-interactive mode (-p) and from Remote Control), and /color (line 61) notes its Remote Control sync behavior.

Verdict: The commands reference page has not been updated to call out Remote Control client availability for the v2.1.110 commands, while it does call this out for /config (added in v2.1.181) and /color. This is a minor inconsistency that would help users discover the v2.1.110 capability, but it is a follow-on improvement rather than the primary documentation gap reported in the issue. The core claim — that Remote Control command support was undocumented — is addressed by the Remote Control page itself.

---

Current State

| Claim | Status |
|-------|--------|
| v2.1.110 changelog commands (/context, /exit, /reload-plugins) documented as Remote Control client commands | RESOLVED |
| /autocompact listed as Remote Control command (claim based on misreading) | RESOLVED |
| Remote Control page has explicit list of commands available from mobile/web | RESOLVED |
| Commands reference page has Remote Control availability notes for the v2.1.110 commands | PARTIALLY RESOLVED |

---

Suggested Fix

N/A — the primary issue has been resolved. The Remote Control page now documents which commands work from mobile and web clients, including all commands from the v2.1.110 changelog.

Optional follow-on improvement (not blocking): add Remote Control client availability notes to the /context, /exit, and /reload-plugins rows in the commands reference table at https://code.claude.com/docs/en/commands, similar to the existing note for /config.

---

References

  • URL: https://code.claude.com/docs/en/remote-control
  • Lines 195-204: "Limitations" section with explicit list of commands that work from mobile and web (/compact, /clear, /context, /usage, /exit, /usage-credits, /recap, /reload-plugins, plus version-specific notes for /mcp and /config)
  • URL: https://code.claude.com/docs/en/changelog
  • Lines 1491-1525: v2.1.110 changelog entry; line 1500 lists /context, /exit, and /reload-plugins as working from Remote Control (mobile/web) clients. /autocompact is not mentioned in this entry.
  • URL: https://code.claude.com/docs/en/commands
  • Line 63: /config row includes Remote Control availability note
  • Line 64: /context row — no Remote Control availability note
  • Line 73: /exit row — no Remote Control availability note
  • Line 107: /reload-plugins row — no Remote Control availability note

---

Conclusion & Recommendation

Primary Concern: The Remote Control documentation did not document which slash commands work from mobile/web Remote Control clients, leaving users unable to discover commands added in changelog v2.1.110.

Resolution Status: RESOLVED

Recommendation: CLOSE

The Remote Control page now contains an explicit, scannable list of commands that work from mobile and web clients, covering all three commands from the v2.1.110 changelog. The reporter's /autocompact reference appears to be a misreading of the changelog, which only mentions /context, /exit, and /reload-plugins. A follow-on enhancement to the commands reference page would be helpful but is not required to close the core documentation gap.

github-actions[bot] · 1 month ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.