Remote & edge nodes

Some work needs the machine that already has the session, the camera, the drive or the serial port. Treating those machines as second-class webhook targets is why most agent platforms cannot do this class of work at all.

• Its identity lines up everywhere — the same UUID in the compose file, the registry, its heartbeat and the database. That consistency is what lets the queue address it exactly like a local bot.
• Desktop worker nodes run on an operator's own machine, driven step by step, with the consequential action gated behind an explicit approval rather than an autonomous click.
• Remote nodes join over a private overlay network instead of being exposed to the internet.
• Adding a machine is an install, not a deployment project — the edge client ships as an npm package.