Why does claude rc not work?

Because rc is not a subcommand. It works as a flag, claude --rc, and as a slash command, /rc, used inside a session you already have open. The subcommand form is spelled out in full as claude remote-control. Typing claude rc at a shell prompt matches nothing.

What does /rc active mean in Claude Code?

It is a status indicator, not a command. While Remote Control is connected, Claude Code shows an /rc active readout in the footer below the input box, and it links to the session on claude.ai. It is hidden when the terminal is too narrow, so a missing indicator does not always mean the connection dropped.

What is the difference between claude rc and claude remote-control?

claude remote-control starts server mode, a process that waits for remote connections and can host up to 32 concurrent sessions. claude --remote-control (or --rc) starts a normal interactive session that is also reachable remotely. Inside a running session, /remote-control or /rc converts that session while keeping its history.

Why is claude remote-control --help returning an error?

Claude Code checks Remote Control eligibility before printing help, so the command errors instead of showing the flag list when you are not signed in with an eligible account.

Which slash commands work from the phone?

Text-output commands such as /compact, /clear, /context, /usage and /recap work, as do /model, /effort, /fast, /color and /rename when you pass the value as an argument. /plugin and /resume are local-only.

claude rc & /remote-control: Full Command Reference

There are four ways to turn on Remote Control in Claude Code: the claude remote-control server command, the --remote-control flag on a normal session, the /remote-control slash command inside a running session, and the same slash command in the VS Code extension. rc is the accepted short form everywhere.

Short answer: run /rc in a session you already have open, or claude remote-control from your shell to start a server that hosts sessions. Both print a session URL you can open on your phone.

All four routes end at the same place. The difference is where you happen to be when you decide you need it.

The four ways to start Remote Control

Where you are	Command	What it does
Your shell	`claude remote-control`	Starts server mode. The process waits for remote connections and can host many sessions.
Your shell	`claude --remote-control` (or `--rc`)	Starts a normal interactive session that is also reachable remotely.
Inside a session	`/remote-control` (or `/rc`)	Converts the session you are already in, keeping its conversation history.
VS Code extension	`/remote-control` (or `/rc`)	Same as above, with a status banner above the prompt box.

Why “claude rc” does not work

If you typed claude rc and got an error, the command is real but the form is not. rc is a shorthand, and it belongs to two of the three ways in, never to the bare subcommand.

You probably typed	What actually works	Where you run it
`claude rc`	`claude remote-control`	Your shell, for server mode
`claude rc`	`claude --rc` or `claude --remote-control`	Your shell, for one interactive session
`claude rc`	`/rc` or `/remote-control`	Inside a session you already have open

The rule underneath it: rc works as a flag (--rc) and as a slash command (/rc). It is not a subcommand, so claude rc matches nothing. The subcommand is spelled out in full as claude remote-control.

Which one you want depends on where you are standing. At a shell prompt, use claude remote-control or claude --rc. Already inside a Claude Code session, use /rc, which converts that session and keeps its history.

Worth knowing while you are here: claude remote-control --help also errors if you are not signed in with an eligible account, because eligibility is checked before help is printed. That one looks like a broken command too, and is not.

What “/rc active” means

If you searched for /rc active, you are almost certainly looking at the footer of an interactive Claude Code session. While Remote Control is connected, Claude Code shows an /rc active indicator below the input box. It is a status readout, not a command you type.

The indicator is a link to the session on claude.ai. Select it with the down arrow key and press Enter to open it.
It is hidden when the terminal window is too narrow to fit it, so a missing indicator does not always mean the connection dropped.
Running /remote-control again opens a status panel with the session URL and a QR code.
If the connection fails, the indicator disappears and a notification explains why. Run /remote-control again to retry.

Typing /rc active as a command does nothing. There is no active subcommand. To check status, look at the footer or re-run /remote-control.

Server mode: claude remote-control

Server mode keeps a process running in your terminal that waits for remote connections. It prints a session URL, and you can press the spacebar to toggle a QR code for scanning with your phone. While a remote session is live, the terminal shows connection status and tool activity.

cd ~/projects/my-app
claude remote-control

Server mode flags

Flag	What it does
`--name "My Project"`	Sets a custom session title shown in the session list at claude.ai/code.
`--remote-control-session-name-prefix <prefix>`	Prefix for auto-generated names. Defaults to your hostname, giving names like `myhost-graceful-unicorn`. The `CLAUDE_REMOTE_CONTROL_SESSION_NAME_PREFIX` variable does the same thing.
`-c`, `--continue`	Resumes the most recent Remote Control session started from this directory. Requires Claude Code v2.1.200 or later.
`--session-id <id>`	Resumes a specific session by ID. Requires v2.1.200 or later.
`--spawn <mode>`	How sessions are created: `same-dir` (default), `worktree` (each session gets its own git worktree), or `session` (serves exactly one). Press `w` at runtime to toggle between the first two.
`--capacity <N>`	Maximum concurrent sessions. Default 32. Cannot be combined with `--spawn=session`.
`--[no-]create-session-in-dir`	Pre-creates one session in the current directory at startup so you have somewhere to type. On by default.
`--verbose`	Detailed connection and session logs.
`--sandbox` / `--no-sandbox`	Enables or disables filesystem and network sandboxing. Off by default.

--continue and --session-id cannot be combined with each other, or with --spawn, --capacity, or --create-session-in-dir.

One gotcha: Claude Code checks Remote Control eligibility before printing help, so claude remote-control --help returns an error rather than the flag list if you are not signed in with an eligible account.

Interactive mode: `claude --remote-control`

If you want a normal terminal session that also happens to be reachable from your phone, use the flag form. Unlike server mode, you can keep typing locally.

claude --remote-control
claude --remote-control "My Project"

--rc is the short form. Passing a name is optional.

From a session you are already in: /remote-control

This is the most common path. You are mid-task, you need to leave your desk, and you want to carry the conversation with you.

/remote-control
/remote-control My Project

Your existing conversation history carries over. Note that --verbose, --sandbox, and --no-sandbox are not available with the slash command. Those are server-mode flags only.

VS Code

In the Claude Code VS Code extension, type /remote-control or /rc in the prompt box, or open the command menu with / and pick it. A banner appears above the prompt box with connection status; click claude.ai/code in the banner to jump to the session. To disconnect, click the close icon or run the command again.

The VS Code command does not accept a name argument and does not display a QR code. The title comes from your conversation history or first prompt.

How the session title is chosen

Claude Code picks the remote session name in this order:

The name passed to --name, --remote-control, or /remote-control.
A title set with /rename.
The last meaningful message in existing conversation history.
An auto-generated name like myhost-graceful-unicorn.

If you did not set a name explicitly, the title updates to reflect your prompt once you send one. Renaming from claude.ai or the mobile app also updates the local title shown in claude --resume.

Turning Remote Control on for every session

By default Remote Control only activates when you ask for it. To auto-connect every interactive session, run /config inside Claude Code and set Enable Remote Control for all sessions to true. Set it to false to never auto-connect, or default to clear your choice and follow your organization or Claude Code default.

The same toggle lives in the Desktop app under Settings, Claude Code, Enable remote control by default, and in the VS Code command menu Settings section from v2.1.203.

With auto-connect on, each interactive Claude Code process registers one remote session. To run several concurrent sessions from a single process, use server mode instead.

Which commands work from your phone

Not every slash command is available remotely. Commands tied to the terminal interface, such as /plugin and /resume, are local-only. These work from mobile and web:

Text-output commands: /compact, /clear, /context, /usage, /exit, /usage-credits, /recap, /reload-plugins
/model, /effort, /fast, /color, and /rename: pass the value as an argument, for example /model sonnet or /effort high
/mcp (from v2.1.166) returns a text status summary on mobile; reconnect, enable, and disable subcommands work from both surfaces
/config (from v2.1.181) accepts key=value from the mobile app; on web it opens your settings instead

Setting up Remote Control: requirements, login, and workspace trust
Using Remote Control from iPhone and Android: the app, QR codes, and push notifications
Troubleshooting Remote Control: every documented error message and its fix
Claude Remote Control: the full guide

claude rc and /remote-control: Command Reference