Blog · September 8, 2026 · 7 min read · by Vilva Athiban P B

Claude Code Remote Control, Explained

The oldest problem with Claude Code is that it works in a terminal and you have a life. You kick off a long task, and now you're tethered: the session is on your laptop, the laptop is on your desk, and the only way to know whether Claude finished — or stalled on a permission prompt twenty minutes ago — is to go look.

Claude Code Remote Control is Anthropic's answer to the tether. It lets you connect to a live, running Claude Code session from the Claude mobile app or a browser — see what it's doing, answer its questions, and steer it — while everything keeps executing locally on your machine. Here's how it works, how to use it well, and where it still leaves a gap that notifications fill.

What Remote Control actually is

Remote Control is not "Claude Code in the cloud." The session stays exactly where it always was: a local process, in your project directory, with your files, your configuration, and your MCP servers. What changes is the front end. When you enable Remote Control, your local Claude Code process registers with Anthropic's API over an outbound HTTPS connection, and the Claude app on your phone (or a browser tab) becomes a second screen for that same session.

Two details matter for the security-minded. First, the connection is outbound only — your machine opens no inbound ports and isn't reachable from the internet. Second, your source code doesn't move to the cloud; the remote client sees the conversation and tool activity, while execution and files remain local.

The workflow it unlocks

The canonical use looks like this: you brief Claude Code on a chunky task at your desk — a refactor, a test-suite cleanup, a long migration — and then you leave. From the sofa, the coffee run, or the school pickup line, you open the Claude app, tap into the session, and check on it. If Claude hit one of its questions ("should I also update the fixtures?"), you answer from your phone and it keeps moving instead of idling until you return.

Recent Claude Code releases have made the remote view considerably more useful: foreground subagent activity now streams live to remote clients, so you can watch tool calls and results as they happen rather than staring at a spinner. Combined with background tasks and subagents, it turns a phone into a legitimate monitoring station for work that used to require sitting at the terminal.

The fine print: limits worth knowing

Remote Control is deliberately conservative, and its constraints shape how you should use it:

  • The terminal must stay alive. Your machine has to remain on and online, with the Claude Code process running. Close the laptop lid without preventing sleep, and the session — and your remote connection to it — goes with it.
  • One remote client per session. Each Claude Code instance supports a single remote connection at a time; this is a personal second screen, not a team dashboard.
  • Reconnection is automatic but not magic. Brief network blips and phone sleep are handled gracefully, provided the underlying local process is still running.
  • Permissions still apply. Remote Control doesn't loosen anything — the same approval prompts appear, just now on a device that's in your pocket.

Remote Control vs. notifications: pull vs. push

Here's the gap. Remote Control is a pull mechanism: it answers "let me check on Claude" brilliantly, but it only helps if you think to open the app. It won't tap you on the shoulder. If Claude finishes — or blocks on a question — while your phone sits face-down, nothing happens until you look.

That's the same problem that exists at the desk, one window away from the terminal, and the fix is the same: a push layer that tells you the moment your attention is needed. We've covered the DIY routes before — hooks-based notifications on the desktop and push alerts to your phone via ntfy, Pushover, or Telegram. The two mechanisms compose beautifully: the notification tells you Claude needs you, and Remote Control lets you act on it from wherever you are, no laptop required.

A sane setup for long-running sessions

  • Prevent sleep before you walk away. On a Mac, caffeinate (or plugging in and disabling sleep on power) keeps the local process alive while you're out.
  • Brief thoroughly, then leave. Remote answering works, but typing detailed course corrections on a phone keyboard doesn't. Front-load the context — our Claude Code tips post covers how — so remote interactions stay short: approve, answer, nudge.
  • Add a push notification for the finish line. Let a notifier watch the session so you don't have to poll the app to learn that the task ended ten minutes ago.
  • Review the diff at a real screen. Approving a permission prompt from a phone is fine; reviewing a 40-file refactor is not. Save judgment calls for the desk.

The bottom line

Remote Control removes the last excuse for babysitting a terminal. Your session runs at home; your control surface rides in your pocket; and with a notification layer on top, the loop closes completely — Claude works, you live your life, and you find out the instant it's your turn again.

Keep reading

Desk Exercises for Programmers: 15 Moves to Do While Your AI Agent Codes

7 min read

Exercise While Coding: Turn Claude Code Wait Time Into Micro-Workouts

7 min read

Claude Code Notch Notifications on Mac: See When Claude Is Done Without Watching the Terminal

7 min read

Claude Code Tips and Tricks: 12 Ways to Use Claude Code Effectively

8 min read

Claude Code Multiple Sessions: How to Run Agents in Parallel Without Losing Track

6 min read

A Claude Code Workflow That Doesn't Involve Watching the Terminal

5 min read

Claude Code Hooks: A Practical Guide to Automating Your Agent Workflow

7 min read

Claude Code Auto Mode: Fewer Permission Prompts Without Living Dangerously

7 min read

Claude Code Subagents: How to Delegate Work to Specialized Agents

7 min read

Claude Code Context Management: Treat the Context Window Like a Budget

6 min read

Per-Subagent Model Selection: Route the Grunt Work Down, Keep the Judgment Up Top

7 min read

Skills and Plugins: How to Teach Claude Code Your Way of Working

7 min read

Claude Code Background Tasks: Run Long Commands Without Blocking Your Session

6 min read

Codex CLI Notifications: How to Get a Ding When Codex Is Done or Needs Input

7 min read

Cursor Notification When Done: Every Way to Get Notified When Cursor Finishes

6 min read

Claude Code Notifications: How to Get Notified When Claude Code Finishes or Needs Your Input

6 min read

Want to Be Notified When Claude Responds? How Claude Notifications Work on Web, Desktop, and Mobile

5 min read

Claude Code Notification Scripts: Copy-Paste Recipes for Every Platform

6 min read

Get a Ding the Moment Codex Needs Your Response

6 min read

Get Notified the Moment Claude Code Is Waiting for Your Input

6 min read

“Notifications Are Turned Off for Claude” — Here Is the Fix

6 min read

Codex Sound When Done: Make Codex CLI Play a Sound When It Finishes

6 min read

terminal-notifier + Claude Code: Native macOS Alerts When Your Agent Finishes

6 min read

Gemini CLI Notifications: How to Get a Sound or Alert When Gemini Finishes

6 min read

Get Claude Code Notifications on Your Phone

6 min read

preferredNotifChannel: Claude Code's Built-In Notification Setting

6 min read

Claude Code Notifications in tmux and Over SSH

7 min read

Claude Code Effort Levels: Why Your Setting Keeps Getting Ignored

8 min read

Codex vs Claude Code Notifications: How Each One Tells You It Is Done

8 min read

Claude Code Notifications Not Working: A Diagnostic Checklist

10 min read

Claude Code Notifications Inside Your Editor's Terminal

7 min read

CLAUDE_CODE_DISABLE_BACKGROUND_TASKS Explained

7 min read

CLAUDE_CODE_DISABLE_BG_SHELL_PRESSURE_REAP Explained

8 min read

Cursor Alerts Explained: Every Alert Cursor Raises, and How to Control Them

7 min read

Claude Code Environment Variables: The Groups That Actually Matter

10 min read

Claude Code Notifications on WSL and Windows

9 min read

Claude Code Checkpoints and /rewind

8 min read

Claude Remote Control: How It Works, Turning It Off, and Auto Mode

7 min read

Claude Code /loop: Poll a Deploy, Babysit a PR, and Get Told When It's Done

8 min read

Setting Up NotchFit With OpenAI Codex CLI: Hooks, $notchfit-plan, and the Daily Flow

7 min read

Claude Mods Explained: What the New Plugin Layer Can Do, and How to Turn On 'You Should Know'

9 min read

NotchFit vs Mac Break Reminder Apps: A Clock or a Signal From Your Coding Agent?

8 min read

Claude Code Headless Mode: Running claude -p in Scripts and CI, and the Three Signals That It Finished

10 min read

Building a Movement Habit at a Desk: Use the Agent Run as the Cue, One Set as the Unit, and Streaks Carefully

8 min read

Claude Code MCP Servers Explained: Adding Servers, Choosing a Scope, Handling Secrets, and Why Long Tool Calls Go to the Background

10 min read

/notchfit:plan Explained: How Claude Code or Codex Writes a Weekly Workout Plan the Notch Can Actually Run

8 min read

Claude Code Spinner Verbs Explained: What “Pondering” and “Brewing” Mean, How to Change Them, and Why You Should Stop Watching the Spinner

7 min read

Why NotchFit's Done and Permission Alerts Wait Until Your Set Ends, When That Costs You, and How to Turn the Workout Off

7 min read

How to Resume a Claude Code Session: --continue vs --resume, Naming Sessions, the Session Picker, Branching, and What Comes Back

9 min read

NotchFit on a Mac Without a Notch: How Pill Mode Works on Mac mini, iMac, Mac Studio and a MacBook With the Lid Closed

6 min read

How to Run a Claude Code Session in the Background: /background, claude --bg, Agent View, and Getting Back to It

9 min read

What a Notch App Can See: NotchFit's Local-First Design, What the Claude Code and Codex Hooks Send, and What Stays on Your Mac

7 min read

Why Codex CLI Asks for Permission Every Time, and How to Tune the Sandbox and Approval Policy Without Going Full Access

8 min read

What to Do While Claude Code or Codex Works: A Simple Protocol for the Two-to-Twenty-Minute Gap in Every Agent Run

7 min read

Is It Possible to Get a Notification When Claude Code or Codex Hits a Reset? Yes for Claude Code: the quota_auto_resume Hooks, Explained

8 min read

What a MacBook Notch App Can Actually Do: The Five Kinds of Notch Utility, Their Trade-offs, and Where NotchFit Fits

7 min read

How to Make MCP Servers Not Take Up as Much Context in Claude Code: Tool Search, alwaysLoad, Scopes and Output Caps

8 min read

The notchfit Command Line: Drive Your Workout, Read Status as JSON, Validate Plans and Test the Notch Without Leaving the Terminal

7 min read