Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

/remote-control

slash never mined documented JSON

A Claude Code slash command, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

Make this session available for Remote Control from claude.ai. Running it while signed out prints that Remote Control requires a claude.ai subscription and tells you how to sign in; before v2.1.206 it reported Unknown command: /remote-control. Alias: /rc

Anthropic's own wording. Read off Commands, captured 2026-09-28.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 149on this box, as of v2.1.308
Written about v2.1.47 first named in a changelog, 18 Feb 2026

In the changelogs

20

Releases whose published page names /remote-control.

  1. v2.1.281
    /remote-control disconnect dialog uses the shared selectable list

    The /remote-control dialog options now wrap around and start focused on Continue

    found in this entry's text, named in this entry

  2. v2.1.268
    '/rc' footer wording and status labels

    Reconnect messages and status labels for /remote-control (/rc) got clearer, more specific wording

    found in this entry's text

  3. v2.1.234
    The idle remote-control upsell moved into the nudge registry

    The idle remote-control suggestion now comes from the shared nudge system; you see the same thing.

    named in this entry, found in this entry's text

  4. v2.1.232
    --project no longer starts a cloud session

    Passing --project alone won't start a cloud session; --ref and --on-branch now need --cloud or --environment.

    found in this entry's text

  5. v2.1.232
    Remote Control stops telling you to reconnect a session another device took over

    When another device takes over your remote session, you're no longer told to reconnect to it.

    named in this entry, found in this entry's text

  6. v2.1.232
    Remote Control tells you when a session was claimed elsewhere

    When another connection claims your session, you're told it ended elsewhere instead of getting a reconnect suggestion.

    named in this entry, found in this entry's text

  7. v2.1.232
    Two remote-control gates for resuming a bridged session

    Resuming a session another process still controls can decline the takeover and tell you why.

    named in this entry, found in this entry's text

  8. v2.1.232
    Remote control can take over a session another process still holds

    Resuming a session another process still holds now tells you to run /remote-control to take it over.

    named in this entry, found in this entry's text

  9. v2.1.232
    Remote Control tells you when another terminal already holds the conversation

    You're now told when another terminal holds Remote Control, and pointed at /remote-control.

    named in this entry, found in this entry's text

  10. v2.1.225
    Remote Control re-mint retry loop and auth-specific failure messages

    Remote Control now retries reconnecting with backoff and tells you to run /login when auth fails.

    named in this entry, found in this entry's text

  11. v2.1.225
    Remote Control auto-revive after re-login

    After you log back in, Remote Control can turn itself back on without you re-running the command.

    named in this entry, found in this entry's text

  12. v2.1.225
    Remote Control disconnect notices point at /login for auth failures

    If Remote Control drops due to auth, the notice now tells you to run /login.

    named in this entry, found in this entry's text

  13. v2.1.225
    Remote Control: new terminal error reasons and clearer failure surfacing

    Remote Control failures now tell you what actually broke and that you can rerun /remote-control to retry.

    named in this entry, found in this entry's text

  14. v2.1.224
    Remote Control disconnects appear in the transcript

    Losing Remote Control now adds a transcript warning hinting at /remote-control to reconnect.

    named in this entry, found in this entry's text

  15. v2.1.223
    Slash commands unavailable in a cloud session explain how to continue locally

    Commands blocked in cloud sessions now tell you the exact local command to run instead.

    named in this entry, found in this entry's text

  16. v2.1.217
    Bridge Fork Session Warning

    found in this entry's text

  17. v2.1.205
  18. v2.1.116
  19. v2.1.51
    Remote Control Bridge Overhaul

    found in this entry's text

  20. v2.1.47
    Remote Control

    found in this entry's text

First cited

7

The earliest release whose published evidence quoted /remote-control was v2.1.47, 18 Feb 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.4718 Feb 2026/remote-control
v2.1.2247 Aug 2026- run /remote-control to reconnect
v2.1.2257 Aug 2026Claude.ai login expired - run /login, then /remote-control
v2.1.2257 Aug 2026run /remote-control to retry
v2.1.23213 Aug 2026already has Remote Control for this conversation · run /remote-control to move it to this terminal
v2.1.2571 Sep 2026Not connected · /remote-control

1 further span in the ledger name it. The list above is the earliest first and stops at 6.

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the slash command does. All slash commands.

Feedback