I Pay $200/mo for Claude Max and Still Can't Use Remote Control
I was excited about Remote Control.
Anthropic announced it on February 25th. Continue your Claude Code session from your phone. Scan a QR code, pick up where you left off. It sounded perfect — I'd been wanting exactly this for months.
So I did what any reasonable person would do. I upgraded to the Max plan. $200/month.
Ran claude remote-control in my terminal.
"Remote Control is not yet enabled for your account."
I refreshed. Logged out, logged back in. Updated Claude Code to the latest version. Tried again.
Same message.
I Wasn't the Only One
I went to the Claude Code GitHub issues page. What I found was... a lot of people having the exact same experience.
GitHub issue #28816: "Returns 'not yet available on your plan' for Max subscriber." Issue #28833: "Remote Control unavailable on Max plan (v2.1.59)." Issue #28884: "Remote Control unavailable for Claude Max subscriber despite eligibility." Issue #29569: "Remote Control not enabled for Max subscriber."
These aren't Pro users confused about plan requirements. These are paying Max subscribers — $100 to $200 per month — who were told they'd get this feature and can't access it.
One user on issue #29764 found something interesting: their Claude Code header showed "Opus 4.6 - Claude API" instead of "Claude Max." The system wasn't even recognizing their subscription correctly.
The best part? Some users get the error "Contact your administrator." It's a personal account. There is no administrator.
The Feature Flag
Digging deeper, someone discovered the feature is gated by a server-side flag called tengu_ccr_bridge. It defaults to false. There's no local override. No waitlist to join. No timeline.
You either have access or you don't. And there's nothing you can do about it.
OK But What About When It Works?
Let's say you're one of the lucky ones. You got through. What then?
The list of limitations is longer than I expected:
Your terminal has to stay open. Close your laptop, session is gone. This isn't a background process — it's a live connection to an active terminal. Your machine goes to sleep? Dead.
10-minute network timeout. Your WiFi drops for 10 minutes? Session is terminated. Start over.
Silent connection drops. This one stung. Users on GitHub issue #28571 report that the iOS app still shows "Interactive" after losing the connection. You type a message, hit send, it looks like it went through — but it never reaches your local session. No error. Just silence.
Stale state after reconnect. Force-quit the app, reopen it, and you might see conversation state from hours ago. Not the current state. No way to recover except starting a new session.
Rate limit kills the connection permanently. Hit the usage cap? Connection breaks. When the cap resets, the connection doesn't come back. You have to start a completely new session — losing all context.
No starting fresh from your phone. You can only continue existing sessions. Want to start a new task from the couch? Can't.
Every action needs a tap. No autonomous mode. No --dangerously-skip-permissions. Every file read, every edit, every command — manual approval. On a phone keyboard.
What I Switched To
I'm biased here — I built it. But I switched to Clautel because it solved the problems I was actually hitting.
It runs Claude Code as a background daemon. I don't need a terminal open. My laptop can be asleep (as long as the machine is awake — I keep it running with the lid closed via system settings).
Each project gets its own Telegram bot. I message the bot, Claude Code runs in that project directory, results come back in the chat.
When I started a session in my terminal earlier that day, I type /resume in Telegram, see my recent sessions with timestamps and previews, and tap one to continue. Full conversation history loads. Or the reverse — /session gives me the ID to continue a Telegram session in my CLI.
The thing I use most that Remote Control doesn't have: /preview localhost:3000. A live screenshot of my dev server, with buttons to click, scroll, and type. From my phone. No port forwarding.
It costs $4/month on top of my Claude Pro subscription. Not $200.
Remote Control Will Get Better
I believe this. Anthropic ships fast. The feature is three days old and explicitly labeled "research preview."
But right now, in February 2026:
- Half the Max subscribers can't access it
- The ones who can face silent disconnects, stale state, and a 10-minute timeout cliff
- Pro users ($20/mo) are completely locked out
- There's no background mode, no new sessions from mobile, and no browser preview
If you want mobile Claude Code that works today, on any plan, with a daemon that doesn't need a terminal window — that's what Clautel does.
npm install -g clautel
clautel setup
clautel start
7-day free trial. Works with Pro, works with Max. And you won't see "not yet enabled for your account."