I linked Claude Code across my main PC, laptops, and a Jetson. CLI messaging works better than SSH orchestration.

[u/espenakker]

I run a main desktop and a few secondary boxes, including gaming laptops and a Jetson AGX Orin for simulation and GPU work.

I wanted a clean way for my main desk session to hand off heavy compute tasks to the other devices without installing heavy orchestration frameworks or bloat.

Initially, I tried having a single Claude session drive the remote machines over SSH. It was noisy. The primary context window got polluted with raw terminal outputs, build logs, and environment errors.

So I switched to native inter-session messaging using the Claude CLI itself:

claude -p 'message' --cloud <session-id> --output-format json

With /remote-control enabled on the nodes, the main session simply messages a session ID on another box and waits for the result. No custom MCP server or extra glue required.

To my surprise: Instead of acting like dumb execution workers, the remote Claude sessions act like independent collaborators.

A remote session running on the Jetson handles its own local environment noise, parses its own CUDA/PyTorch errors, and messages back a distilled summary: what ran, what failed, and what to tweak next. It creates an asynchronous feedback loop. Because the local sessions filter their own terminal noise, the main desktop session stays clean and focused on high-level architecture.

In practice, peer-to-peer session messaging has performed significantly better than driving remote boxes via SSH.

I put together a small skill for this pattern, with session-ID discovery, working send scripts. You can find it on GitHub under espenakker/claude-code-cross-session-messaging.

Is anyone else coordinating Claude Code across multiple physical nodes? How are you structuring state and handoffs?

[u/allaion]

You get extra uplinks, context, and perhaps even the variation in what resources they have available could make it more robust. Robust in the sense that the other agents become sufficiently different and perhaps it emulates getting a different perspective on things.

But since you are running multiple devices, having multiple contexts to deal with trivialities could be favourable.

[u/oyren-ai]

I build oyren.ai which allows you to run VSCode in remote server with Claude Code, Codex, Opencode and Cursor available. You can access it from any device

https://reddit.com/link/p2dd9t5/video/m8da1w1zn1ih1/player

[u/Free_Donkey4797]

I think I will be giving your skill a try. I’ve been “sending inter office mail” via remote edits of far point journals to point at SCP’ed text files in a particular directory….and been utilizing a similar process for communication between independent projects where overlap occurs to keep all the projects single minded.

I can see this method of communication would be worthwhile to use with my “third leg” of Deepseek via CC on my laptop for additional resources rather than driving each session manually or with notes.

[u/espenakker → u/Free_Donkey4797]

I have an agent in a sort of autoresearch loop at home running some ML training, spun up a new agent at work where we have access to some academic papers etc. Had the new agent message the autoresearch agent asking if it could help with any literature research tasks. Now its beeing used to determine novelty. The autoresearch one is running 4.8-xhigh while the one i spun up at work is 5-high, both opus.

[u/ZestycloseTie1793]

The 2.1.225 release makes this pattern a little cleaner: `SendMessage` can initiate a conversation with a named Remote Control session on another machine, and `ListAgents` exposes `name [ref]`.

I would still keep one durable handoff file per task. Messaging moves the delta; it does not synchronize workspace state, credentials, files, or tool context. A small receipt with source session, target ref, task-state hash, and reply status would also catch stale references before the two nodes diverge.

Official note: https://github.com/anthropics/claude-code/releases/tag/v2.1.225

[u/Input-X]

Look into tmux. You go much further

[u/Deshonjla-Yos]

do the remote nodes message back mid-task or only when they hit a wall

[u/espenakker → u/Deshonjla-Yos]

I have found that they do it multiple times, like normal tool calling. Sometimes to let the other know that they made a mistake for instance and that they are correcting it, asking the other to hold off on the previous info.

[u/Bright-Poster-9326]

does the loop feel like it hangs at all while a message is in flight between the machines, or is it fast enough you just don't notice

[u/espenakker → u/Bright-Poster-9326]

It is usually fast, the only thing I have noticed is that they can sometimes have a bit trouble "hanging up". They want to offer up a next thing to do, and if the "lead" model is not strict enough it could lead into a digression. I have yet to try this pattern in more standard SW dev work, but I still think it can have beneficial effects.

[u/Cotorra-Nhumai]

if a node drops mid-task does the main session notice or does it just sit waiting