Basically if you start up a claude terminal session, you can enable remote control for that one time, or you can go to /config and change the global setting so that by default each session will be auto-connectable
You can connect via claude.ai/code on the web, or via the mobile app.
You can't connect via the web/app to VS Code sessions, and you can't connect to sessions created by Claude SDK.
One thing it does not do is let you create new sessions. So if you have a heavy remote first workflow (like you work from your phone a lot). People who are used to tmux/tailscale/termius etc or other mobile wrappers/orchestrators won't find this very useful (yet).
The architecture here is right, local execution, remote window. Running agents on your own machine means your filesystem, tools, and env stay intact, you're not paying cloud rates for compute that your hardware can already handle.
The "survive interruptions" piece is underrated. Anyone who has had a long agentic run get killed by a dropped connection knows the pain. Session persistence isn't glamorous but it changes how you actually use these tools day to day.
Curious how it handles multiple local sessions — if you're running separate agents on the same machine for different projects, can you switch between them remotely or are you stuck being able to only remote control 1 bot?
Ok, this is nice, but if that terminal running CC is open on VS code for example, does it work?
I tested it out a bit.
Basically if you start up a claude terminal session, you can enable remote control for that one time, or you can go to /config and change the global setting so that by default each session will be auto-connectable
You can connect via claude.ai/code on the web, or via the mobile app.
You can't connect via the web/app to VS Code sessions, and you can't connect to sessions created by Claude SDK.
One thing it does not do is let you create new sessions. So if you have a heavy remote first workflow (like you work from your phone a lot). People who are used to tmux/tailscale/termius etc or other mobile wrappers/orchestrators won't find this very useful (yet).
I wrote a bit more about this here: https://yepanywhere.com/claude-code-remote-control.html
The architecture here is right, local execution, remote window. Running agents on your own machine means your filesystem, tools, and env stay intact, you're not paying cloud rates for compute that your hardware can already handle.
The "survive interruptions" piece is underrated. Anyone who has had a long agentic run get killed by a dropped connection knows the pain. Session persistence isn't glamorous but it changes how you actually use these tools day to day.
Curious how it handles multiple local sessions — if you're running separate agents on the same machine for different projects, can you switch between them remotely or are you stuck being able to only remote control 1 bot?
per the docs each instance gets its own remote control session and environment, so it should handle multiple CC instances.