When using Claude Code day to day, you inevitably run into situations where you want to check a running session on the go, or keep controlling it after stepping away from your PC. That is where /rc (Remote Control) comes in.
However, Claude Code offers several remote features, leading many to ask: "How does it differ from dispatch?" or "When should I choose Remote Compute?" This article focuses on /rc, clarifying its mechanism, usage, and differences from other features.
Basics of /rc (Remote Control)
/rc (officially /remote-control) is a command that enables you to control locally running Claude Code sessions from other devices.
Executing it displays a session URL and QR code. By simply opening it in a browser on your smartphone, tablet, or another PC, you can join the same session directly. Conversation history and tool execution permissions are completely preserved, making resuming work seamless.
Crucially, neither code nor files are sent to the cloud. Because it simply connects a remote interface to the Claude Code session running on your local machine, it is secure.
Usage is remarkably straightforward.
# Step 1: セッションに名前をつける（任意だが推奨）
/rename "feature-auth-refactor"
# Step 2: Remote Control を起動
/rc
# → URL と QR コードが表示される
# → スマホで QR を読み取るか、ブラウザに URL を入力して接続Naming it with /rename lets you immediately identify which session to enter when running multiple sessions.
Behavior across client environments
Claude Code can be used across three environments: terminal, desktop application, and web (claude.ai/code). The behavior of /rc varies slightly across each.
Terminal version (CLI)
The most quintessential use case. Running /rc in the terminal prints the URL and QR code directly. Scanning the QR code on your phone while out connects you immediately.
Desktop app version (Mac / Windows)
Because the desktop app includes built-in session management UI, destination management after launching /rc is even smoother. Actions such as selecting from a list of already running sessions to switch to the Web UI are simple.
Web version (claude.ai/code)
Because the web version already runs in the browser, /rc is rarely needed, as you can access the same session by visiting the same URL from another device's browser. Where /rc truly shines is when exposing terminal or desktop app sessions tied to a local machine externally.
Comparison with similar tools and features
Claude Code provides three remote features. Because each solves a distinct problem, it is important not to conflate them.
| Item | /rc（Remote Control） | dispatch | Remote Compute |
|---|---|---|---|
| Execution environment | Local machine | Local machine | Anthropic Cloud |
| Primary use case | Control existing sessions from other devices | Automated asynchronous task execution | Offloading long-running tasks |
| Conversation sync | Real-time sync across devices | Accumulates in Cowork tab | Independent session |
| Access to local files | Available | Available | None (cloud environment) |
| MCP servers | Available | Available | Limited |
| Persistence after closing app | Not possible (local dependency) | Depends on task | Continues |
In summary:
/rc= Mobility. "I want to interact with my currently running session from another location."- dispatch = Automation. "I want to hand off a task and review results when it finishes."
- Remote Compute = Cloud offloading. "I want work to continue even after I close my laptop."
The decision criteria when in doubt are simple: choose /rc or dispatch if you need your local environment (files, MCP, credentials); choose Remote Compute if you do not need it and tasks run for a long time.
While SSH clients like Termius also allow remote terminal access, they offer only generic access to the entire terminal. /rc is purpose-built for Claude Code sessions (conversation + tool execution context), providing the unmatched convenience of instant QR code connectivity.
Practical use cases
1. Operating sessions during meetings
Delegate a large-scale refactoring to Claude Code and head into a meeting. Even if Claude asks to confirm specifications for a function mid-way, you can respond instantly from your smartphone. Work never stalls, enabling a workflow where the task is complete by the time you return to your desk.
2. Monitoring progress on long-running tasks
Tasks like test suite runs or build monitoring don't require being glued to your PC, yet you still want to keep an eye on them. Connecting via /rc lets you monitor progress from your living room sofa and step in if errors occur.
3. Code reviews from another device
Review PR diffs generated by Claude on a tablet and issue modification instructions. Because the local environment remains directly accessible, instructions like "open that file and verify" execute smoothly.
4. Session sharing within teams
Sharing the session URL allows colleagues to see what Claude is currently doing. Being able to share status via text without launching screen-sharing tools is a subtle yet powerful benefit.
Security and considerations
By design, /rc does not transmit code to the cloud, providing strong security assurance. However, several key points should be kept in mind:
- Treat session URLs as confidential information. Anyone with the URL can access the session, so avoid posting it to public channels.
- Dependent on local machine status. If your PC goes to sleep or loses network connectivity, the remote connection drops as well.
- Supported plans: Available on Pro, Max, Team, and Enterprise (not available with API keys alone).
Conclusion
/rcis a command for "controlling local sessions from other devices." Code stays local.- It solves different problems compared to dispatch (automation) and Remote Compute (cloud execution).
- Most powerful in the terminal version. Instant connectivity from smartphones via QR code is its core strength.
For the overall Claude Code workflow, see this article; for a comparison with Cursor, see this post.
At GleamHub, we support building development workflows powered by AI tools like Claude Code. If you want to introduce AI agents into your development process or establish a remote development environment, please feel free to consult with us.
