Skip to content

The swarm

Neutron is not one deployment you visit. The direction is several nodes that talk to each other: a hub instance that can drive peer instances, plus a companion program on a personal machine that can see and use the screen.

hub instancethe control nodepeer instanceanother team's neutronpeer instanceanother environmenta desktopscreen, input, voiceone authenticated interface for all three

The desktop companion is a separate Rust program with its own safety rails —it releases the mouse if the cursor drifts too far, and caps how long and how many actions a session may take.

Peers and desktops are reached through the same authenticated interface, so remote control is not a second, weaker access path bolted on beside the governed one.

Why this shape

The obvious alternative — one big server everyone logs into — cannot do the thing people actually want, which is an agent that acts where the work is. Some work is on a server. Some is on the machine in front of you, inside applications that have no API.

Splitting the system into nodes has three consequences worth stating plainly:

Desktop control becomes legitimate. It runs on a local node you own, not on shared infrastructure, so it is a connector rather than a liability.

The hub needs its own governance. One instance driving another is exactly the escalation path an attacker would want, which is why it uses the same authenticated interface and the same gates as everything else rather than a private side channel.

The rails move to the edge. The desktop companion enforces its own limits locally — drift detection on the mouse, caps on session length and action count — because a network round-trip is too slow to stop a runaway input loop.

The desktop companion is written in Rust and shipped separately from the platform. Its core is working and live-verified: screenshots, input injection, accessibility-tree perception, and a voice leg.