Remote Control dialog now says when it isn't connected

The /remote-control dialog now shows when Remote Control isn't connected or needs a claude.ai sign-in, instead of assuming it is connected

You'll noticeTier: how much it should matter to you

2Useful: my rating, 1 to 5

1Signal: worth watching, 1 to 5

Remote ControlArea: what it touches

ImprovementsKind: in v2.1.318, 03 Nov 26

ImprovementsSection of the release

What

Remote Control lets you reach a Claude Code session from claude.ai. The dialog opened by /remote-control used to assume the session was connected. It can now show a problem state instead, with messages such as:

"Remote Control isn't connected."
"Remote Control needs a claude.ai sign-in."

The dialog also has a "QR code unavailable" option. The Disconnect item now explains that disconnecting can archive the session straight away and stop a later --resume from reconnecting it.

Why

If your connection has dropped or you are not signed in, you now see why, instead of a message suggesting everything is connected.

Read from

Names in the bundle/remote-control

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeFixed /remote-control showing a session as available after a failed connection

See this entry in the whole of v2.1.318 →

The build it came inv2.1.318

3 Nov 2026 · 425 entries, this one is #167.

Use it now23
You'll notice215
Nothing to try yet27
Under the hood160

Either side of it

v2.1.317Older

Open the release →

Names in this entry

slash/remote-control
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
cli--resume
Resume a specific session by ID or name, or show an interactive picker to choose a session. In place of an ID, you can pass the absolute path to a session's .jsonl transcript file. The picker and name search include sessions that added this directory with /add-dir. When you pass a session ID, Claude Code searches the current project directory and its git worktrees, then every other project on this machine. Before v2.1.223, the ID search covered only the current project directory and its git worktrees. Background sessions appear in the picker marked with bg. Resuming one that is still running opens that session in this terminal through claude attach, and a prompt you pass on the command line goes to it as its next turn. Before v2.1.285, Claude Code refused and printed the claude attach command to run instead

Anthropic's note

Upstream's own release notes for v2.1.318 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Fixed /remote-control showing a session as available after a failed connection

Is this right?