Claude Code’s Remote Control Won’t Last a Cigarette Break.

”Ship Before You Hype” Series #3

The Official Copy Was Beautiful

Anthropic’s own words:

“Take a walk, see the sun, walk your dog without losing your flow.”

Walk your dog. See the sun. Don’t lose your flow. Great copy.

X ran with it.

“Genuinely too convenient. Just open a URL in your browser.” “Continue working from your phone on the train.” “Relax and check progress from the couch on your tablet.”

I took a walk. Smoked a cigarette. Came back.

Dead.

Getting Connected Is Already Annoying

Here’s the connection flow.

Type /remote-control in the terminal. A URL and QR code appear. Scan it on your phone, open it in a browser or the Claude app.

Sounds simple on paper. In practice, friction everywhere.

First, there’s no clean way to get the URL to your phone. Read it off the terminal and type it by hand? The QR code exists, but the Claude app doesn’t launch a camera. You open your camera app, scan the QR, open the browser, then redirect to the Claude app. Too many steps.

The connection experience is already mediocre. Are the people calling this “too convenient” actually doing this flow every time?

Five Minutes and It’s Gone

Connected. So far, so good.

Instructions from the phone reach the terminal. While connected, it works. Acknowledged.

Here’s where it falls apart.

Step outside for a smoke. Five minutes. Come back. Disconnected. Reconnect. Disconnected again.

Someone wrote “it auto-reconnects even when sleep or network is unstable.” It doesn’t. The session is dead. Get a new URL. Scan a new QR. Start over.

If you call yourself “remote,” survive a bathroom break. A remote that dies in five minutes isn’t remote. It’s a wired headphone.

Discord Is Just Better

For “controlling Claude Code from your phone,” --channels via Discord is overwhelmingly superior.

Discord is always connected. Close the app, notifications still come. Sessions don’t die. A bot mediates the connection, so it doesn’t depend on the phone’s connectivity.

Remote Control is a direct connection between phone and terminal. The moment the phone side hiccups, it dies. Discord puts a bot in the middle — asynchronous. The phone can sleep; the terminal keeps working.

Architecture settled this before it started.

Nothing Worth Praising

In this series, every tool got at least one genuine compliment.

Channels had Mac mini flat-rate economics. Stitch had 10-second Figma sharing.

Remote Control has nothing.

“Instructions arrive while connected” is not a feature. “Phone calls transmit voice while connected” — that’s the same sentence. It’s a minimum spec, not a value proposition.

Connection is tedious. It disconnects fast. Reconnection is manual. Every part of the experience is half-baked.

The only meaningful thing Remote Control accomplished was confirming that Discord was the right choice. As a cautionary tale, it was excellent.

Ship Before You Hype

The official copy says “take a walk.” X says “too convenient.” Nobody writes “dies in five minutes.”

They either haven’t tried it, or they tried it and never left their desk long enough to notice.

I don’t hand out blueprints. I showed you where the walls are. How to climb them is your problem.

Everyone has their own We ship. We own.