NebLink

Device interconnect: pair machines, run tools across devices, transfer files.

NebLink connects your devices (macOS, Linux, Windows) into a synchronized mesh. Once paired, agents on one machine can execute commands, read and edit files, and transfer files on another — a laptop can drive a lab workstation without SSH setup.

Pairing a Device

  1. Sign in to nebflow.space with your nebflow account
  2. In the Nebflow client, open the NebLink section in settings and sign in — the device enrolls itself under your account
  3. Repeat on each device. Devices under one account form a network; a default network is created automatically on first registration

Enrollment produces a long-lived device credential stored at ~/.nebflow/neblink/device.json with owner-only file permissions. The raw device token exists only in this file — the server stores just its hash.

Cross-device Tools

Agents run familiar tools on a remote device by setting the tool's device parameter:

| Tool | Remote behavior | |------|-----------------| | Bash | Execute shell commands on the target device | | Read / Write / Edit | File operations on the target device | | Glob / Grep | Search the target device's filesystem | | TransferFile | Copy files between devices |

From the agent's perspective these are the same tools — results and errors come back as if run locally, tagged with the remote device's name.

Connectivity: Direct and Relay

Two link types, chosen automatically:

  • Direct — devices on the same local network discover each other and connect peer-to-peer
  • Relay — when devices are on different networks, traffic is relayed through the NebLink server over a persistent WebSocket tunnel

Either way the tool interface is identical; the transport is transparent to the agent.

Checking Device Status

Your profile page lists every device in your networks with its online status — useful to confirm a machine is reachable before assigning it remote work.