`src/content/posts/2026-02-24-remote-control-claude-code-from-your-phone.md`

100 lines

---
title: "24/7 Agents, Zero Desk Time: Remote-Controlling AI Sessions From Your Phone"
description: "A new feature lets you start a coding session on your machine and continue it from your phone. For anyone running always-on agents, this changes everything."
date: 2026-02-24
tags: ["ai", "automation", "infrastructure"]
author: "Agent Abrams"
---

The moment I saw [Noah Zweben's tweet](https://x.com/noahzweben/status/2026371260805271615) this morning, I stopped what I was doing.

## Watch the Video

[**Subscribe to @AgentAbrams on YouTube**](https://youtube.com/@AgentAbrams) for new videos every week.

> "Start local sessions from the terminal, then continue them from your phone. Take a walk, see the sun, walk your dog without losing your flow."
> -- [@noahzweben](https://x.com/noahzweben)

There is now a **Remote Control** feature for AI coding sessions. If you are anything like me -- someone who runs dozens of autonomous agents on a server and checks terminal output more than text messages -- this is a big deal.

![hero](/images/heroes/remote-control-claude-code-from-your-phone.png)

## What It Does

The feature connects your running terminal session to a web or mobile interface. You get a session URL and a QR code. Scan it with your phone, and you are in.

Here is the key: **it is not a new session**. It is your *exact* session -- same conversation history, same context, same file access. The mobile interface is just a window into what is already running on your machine.

That is fundamentally different from starting a fresh chat on your phone. Context is everything when you are deep in a build, and losing it means starting over. Remote Control preserves it all.

## Why This Matters If You Run Always-On Services

I run a fleet of agents on a single server. They handle everything from automated publishing to data pipelines to visualization builds. The pattern was always the same:

1. Connect to the server
2. Start a session
3. Build something complex over 30-60 minutes
4. Realize I need to step away
5. **Lose the session context**

Step 5 was the killer. I have lost count of how many times I had to reconstruct a session from version history and process logs because I closed my laptop.

With Remote Control, the flow becomes:

1. Connect to the server
2. Start a session
3. Build something complex
4. Scan a QR code with your phone
5. **Walk the dog while monitoring the build**

The session stays alive. If your laptop sleeps or your network drops, it reconnects automatically when your machine comes back online.

## How It Works

The session runs on your local machine or server, not in the cloud. Your files, your environment, your credentials -- all stay local. The phone is just a remote viewport. Nothing gets transferred to a third party.

| Feature | Detail |
|---------|--------|
| Session persistence | Full context preserved across devices |
| Reconnection | Automatic after network drops |
| Security model | Everything stays on your machine |
| Requirement | Pro or Max subscription |

## What I Want to See Next

This is still a research preview, so it will evolve. My wishlist:

- **Push notifications** when a long-running task completes -- imagine getting a ping that says "your build finished, 10 pages generated"
- **Multi-session switching** -- I run multiple agents and being able to jump between active sessions from my phone would be powerful
- **Voice input** -- dictating feedback while walking would save real time

## The Bigger Picture

This feature is part of a larger trend: **the terminal is becoming ambient**. We are moving from "sit at a desk and type commands" to "start a process and check in from anywhere."

For anyone running autonomous services, this has been the missing piece. The agents run around the clock. Now the operators can stay connected without being chained to a desk.

## The Takeaway

If you are building anything that runs in the background -- agents, automation, data pipelines -- the ability to monitor and steer those systems from your phone is not a convenience. It is a workflow shift. It means you can start ambitious, long-running tasks without blocking your entire day. It means fewer lost sessions, fewer context rebuilds, and less anxiety about stepping away from the keyboard.

The best infrastructure lets you walk away from it. This gets us closer to that.

## Credit

Thanks to [Noah Zweben (@noahzweben)](https://x.com/noahzweben) for sharing this. The feature is currently rolling out in research preview.

---

**Let's Connect**

- [**@agentabrams on X**](https://x.com/agentabrams) -- DMs open
- [**goodquestion.ai**](https://goodquestion.ai)