[FEATURE] Remotely initiate and control NEW Claude Code sessions on REGISTERED DEVICES

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude Code's Remote Control is useful for accessing a running Claude Code session from another device, but the workflow requires the session to be initiated from the machine where Claude Code is installed.

For users who have Claude Code installed on multiple always-on machines—such as VPSs, development servers, workstations, or home computers—there is no convenient way to remotely initiate a new Claude Code session on one of those machines.

For example, if I have Claude Code installed and authenticated on my VPS, I currently need to SSH into the VPS, start Claude Code, and then establish remote access. This defeats much of the convenience of having an always-on

Proposed Solution

Allow authenticated Claude Code installations to register themselves as available devices associated with a user's Claude account.

From Claude's web or mobile interface, the user could:

See their currently online Claude Code devices.
Select a device.
Select or specify a working directory/project.
Start a new Claude Code session remotely.
Interact with that session through the existing Remote Control interface.

For example:

Claude Code Devices

🟢 Company VPS
/srv/containers

🟢 MacBook Pro
~/Projects

⚫ Home Server
Offline

Selecting Company VPS → /srv/containers → Start Session would launch Claude Code directly on the VPS and connect the user to it.

The existing Claude Code installation would remain responsible for executing commands and accessing the local filesystem. The new functionality would simply provide a secure way to initiate and connect to sessions remotely.

Alternative Solutions

Provide a lightweight Claude Code host/agent mode that can run continuously on a machine and maintain an authenticated connection to the user's Claude account.

The host would advertise itself as an available Claude Code device and wait for session-start requests. When a request is received, it launches Claude Code in the requested project directory and establishes the remote session.

This could also be exposed as a simple CLI command such as:

claude host

or:

claude --remote-host

This approach would be particularly useful for VPSs, Clouds and development machines that are intended to remain online continuously.

The key distinction from the current Remote Control workflow is that the user should be able to initiate the session remotely, rather than having to first log into the target machine and start Claude Code there.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

I have Claude Code installed and authenticated on my VPS, which is always online and hosts my development projects and infrastructure.

I'm away from my computer and notice that one of my services may have an issue.
I open Claude from my phone.
I go to my registered Claude Code devices and see that my VPS is online.
I select the VPS and choose the relevant project directory.
Claude Code starts a new session directly on the VPS.
I ask Claude to inspect the service, check the logs, and identify the problem.
Claude Code performs the work directly on the VPS because the session is running on that machine.
I can then continue the session from my phone or switch to my Mac later and continue working.

Today, I would need to SSH into the VPS first, start Claude Code manually, and then establish Remote Control.
No need to explain that from my phone, it's not an easy task 😅.
This feature would remove that unnecessary step and make always-on machines genuinely accessible as Claude Code workstations.

Additional Context

_No response_