Anthropic Rebuilds Claude Code Desktop App Around Parallel Sessions

[McScooby]

You're guessing wrong. I was on the Pro plan and then upgraded to the £90 a month plan when I started getting maxed, that too gets limited within hours of we starting work.

Take a look at the Claude subreddit r/ClaudeAI and you'll see thousands of people like me all frustrated that our plan limits have been slashed massively in the last few weeks.

Cool, am thinking about giving Perplexity Computer a shout or that abacus ai (although can't figure out why this is so cheap) I haven't been onto the sub-reddit yet as just finding my way about which is working well, one thing I do know is Apple better hit it out the park at WWDC, but my gut tells me they are years behind especially when comparing Apple Maps to Google - Google obv had the head start, but in the same timeframe that Apple Maps has been about Google pretty much made Streetview prevalent everywhere, Look Around can't even touch it now. I fear it may be the same with AI, but happy to be proved wrong.

 

[Jest3r]

I'm interested in this claimed SSH support. Last time I checked, remote SSH only worked via Claude API on a completely separate billing structure.

 

[McScooby]

I'm interested in this claimed SSH support. Last time I checked, remote SSH only worked via Claude API on a completely separate billing structure.

From its mouth;

Yes, this has changed significantly. What you're thinking of — the old model where SSH-style remote access required a separate API key on a separate billing structure — is no longer the primary approach. Here's the current picture:

Remote Control (the new official way)

Remote Control is now available on all claude.ai plans (Pro, Max, Team, Enterprise) — no API key or separate billing needed. It connects claude.ai/code or the Claude mobile app to a Claude Code session running on your local machine. Claude

Crucially, API keys are not supported for Remote Control — it requires claude.ai OAuth authentication. If you have ANTHROPIC_API_KEY set in your environment, you'd need to unset it first. Claude

So the billing structure has essentially flipped: the new first-class remote access is tied to your claude.ai subscription, not the API.

What it does

When you start a Remote Control session, Claude keeps running locally the entire time — your filesystem, MCP servers, tools, and project config all stay available. The web and mobile interfaces are just a window into that local session, not cloud execution. Claude

You start it with claude remote-control (server mode) or claude --remote-control (interactive session), and it gives you a session URL and QR code to connect from any device.

If you still want API-key-based headless/remote usage

The AI model still runs on Anthropic's servers either way, but the local Claude Code process handles context management, file operations, and tool execution. Claude Fast You can absolutely still SSH into your Mac Studio and run claude there with an API key for headless/scripted use — that still works. But the slick "continue from your phone" remote session experience now requires the claude.ai login path.

TL;DR for your setup: If you have a Claude Pro/Max subscription, Remote Control is now included — no separate API billing needed for remote sessions. The old requirement for a separate API key for remote access is gone for this use case.

 

[73CortinaV8]

More threads means more token$ burned

 

[macduke]

I just want to be able to sign in with both my work and personal accounts and easily switch between them!

 

[svish]

Good to know about all the changes happening. Don’t think I have a need for this but still impressive to see the changes being implemented.