Claude Code Remote Control ガイド

入門 6 min

Remote Control（2026-02）でターミナルセッションを開始し、QRコードスキャンでモバイルから制御します。アウトバウンドポーリングのセキュリティ設計、マルチセッション監視、実践ワークフローを解説します。

Remote Controlモバイルセッションモニタリング

Remote Controlのセットアップ

Remote Control is available for Pro and Max subscribers. To start a remote session, use the /remote-control command in your terminal. Claude Code generates a QR code that you scan with the Claude mobile app. The session syncs instantly — you see the same conversation, file changes, and tool outputs on your phone as on your terminal. The key architectural insight is that your machine never opens inbound ports. Instead, it polls Anthropic's API for instructions via an outbound connection. Your files, MCP servers, and local tools stay on your machine — only chat messages and tool results flow through the encrypted bridge. You can optionally set a custom session name for easy identification when monitoring multiple sessions: /remote-control --name 'auth-refactor'. This name appears in the Claude mobile app's session list.

# Start a remote control session
claude /remote-control

# Start with a custom name
claude /remote-control --name "auth-refactor"

# QR code appears in terminal — scan with Claude mobile app
# ┌─────────────────────┐
# │ ▄▄▄▄▄ █ ▀█▀ ▄▄▄▄▄  │
# │ █   █ █▀▄▀█ █   █  │
# │ ▄▄▄▄▄ █ ▀▄▀ ▄▄▄▄▄  │
# └─────────────────────┘
# Session URL: https://claude.ai/code/session/abc123

セキュリティアーキテクチャ

Remote Control uses outbound polling, meaning your local machine connects out to Anthropic's servers — there are no inbound connections, no open ports, and no network configuration required. This is a fundamental security advantage: your machine is never directly addressable from the internet. All communication is encrypted in transit. Your local filesystem, MCP servers, environment variables, and project configuration never leave your machine. Only the conversation text, tool call requests, and tool results are transmitted. The session is authenticated to your Anthropic account, and the QR code contains a one-time token that expires after a short window. For enterprise environments, note that all code execution happens locally. If your organization has firewall rules, Remote Control only requires outbound HTTPS (port 443) to api.anthropic.com — the same connection Claude Code already uses for model inference.

# Security architecture
┌──────────────────────┐     HTTPS (outbound only)     ┌──────────────┐
│   Your Machine       │ ─────────────────────────────▶ │  Anthropic   │
│                      │ ◀───────────────────────────── │  API         │
│  - Files stay here   │     Encrypted chat + results   │              │
│  - MCP servers here  │                                │              │
│  - .env stays here   │                                └──────┬───────┘
│  - Code runs here    │                                       │
└──────────────────────┘                                       │ HTTPS
                                                               │
                                                        ┌──────▼───────┐
                                                        │  Your Phone  │
                                                        │  Claude App  │
                                                        │              │
                                                        │  - View only │
                                                        │  - Approve   │
                                                        │  - Instruct  │
                                                        └──────────────┘

# No inbound ports. No VPN. No port forwarding.
# Works through corporate firewalls (same as normal Claude Code).

モバイルワークフロー

Remote Control shines in specific workflows where you need to stay connected but don't have your laptop open. The most common use case is fire-and-forget: start a large refactoring or migration task in your terminal, close the lid, and monitor progress from your phone during your commute. From your phone, you can see Claude's real-time actions, approve or reject file changes, provide additional instructions to redirect work, and monitor multiple sessions simultaneously. This makes it perfect for reviewing Claude's work during downtime — waiting in line, during lunch, or between meetings. Another powerful workflow is overnight tasks. Start a long-running task before leaving work, and check in from your phone at home. If Claude needs input (choosing between approaches, confirming a destructive operation), you can respond immediately rather than finding it blocked the next morning.

# Workflow 1: Fire-and-forget migration
# Terminal (before leaving desk):
claude "Migrate all REST endpoints to GraphQL resolvers"
claude /remote-control --name "graphql-migration"
# Close laptop, monitor from phone

# Workflow 2: Multi-session monitoring
# Terminal 1:
claude /remote-control --name "frontend-refactor"
# Terminal 2:
claude /remote-control --name "api-tests"
# Phone: switch between both sessions in Claude app

# Workflow 3: Overnight code review
# Terminal (end of day):
claude "Review all PRs opened today and leave comments"
claude /remote-control --name "pr-review"
# Check in from phone at home, approve/modify reviews

ヒントとトラブルシューティング

For the best experience, ensure your machine stays powered on and connected to the internet. Sleep mode will pause the session — the mobile app will show a 'session paused' indicator and resume automatically when your machine wakes up. If the QR code expires before you scan it, simply run /remote-control again to generate a new one. Each QR code contains a one-time token with a short expiration window for security. For long-running tasks, consider using claude --continue with Remote Control. This lets you resume a previous session from your phone even if the terminal process was interrupted. Your conversation history and context are preserved. Network considerations: Remote Control works on any network that allows outbound HTTPS (port 443). It works through most corporate firewalls, VPNs, and NATs without additional configuration. If you experience connectivity issues, verify that api.anthropic.com is not blocked by your network.

# Resume a remote session after restart
claude --continue --remote-control

# Check active remote sessions
claude sessions list
# ID        Name              Status    Connected
# abc123    auth-refactor     active    phone + terminal
# def456    pr-review         paused    terminal only

# Troubleshooting: test connectivity
curl -s https://api.anthropic.com/v1/messages \
  -H "x-api-key: test" 2>&1 | head -1
# Expected: HTTP 401 (reachable but unauthorized = OK)

実行プレビュー

Claude Code Remote Control ガイド