Remote Control

Nico runs in the cloud, but can reach back into your machine. Pair a local device and the cloud runner can execute runs against your local code, drive your dev server and stream logs back — so you can build and test a motion locally, then ship it.

Cloud runner

Provisioned when you
pair your first device

not set up

encrypted tunnel

wss://bridge.macrodeep.com

Local device

No device paired yet

offline

1Install bridge

2Pair device

3Allow & run

The bridge runs on your machine with your user permissions. The cloud runner can only do what you allow below — start narrow, widen as you trust it. Every remote action is streamed to the run timeline and audited.

1 · Install the local bridge

A tiny daemon that opens an outbound, encrypted tunnel to the cloud runner. No inbound ports, no firewall changes.

macOS

Linux

Windows

$ brew install macrodeep/tap/nico-bridge && nico bridge up

Already installed? The bridge auto-starts on login — jump to pairing.

2 · Pair this device

Generate a one-time code, then approve it from the bridge running on your machine. Codes expire in 5 minutes.

••••••

Pairing code
expires in 5:00

3 · What the cloud runner may do locally

Scopes the remote runner gets on a paired device. Writes are staged for review unless you turn that off.

Run shell commands exec

Start runs, run tests and scripts in the paired workspace.

Read workspace files fs.read

Read code and config in the mounted project directory.

Write & edit files fs.write

Apply code edits and write artifacts back to disk. Staged for review.

Control dev server & ports net.forward

Start/stop the local dev server and forward localhost back to the cloud preview.

Read local secrets env.read

Inject .env values at run time. Never streamed to logs. Off by default.

Remote session

Trigger a cloud run that executes on your paired machine and streams back here in real time.

Run on local from the cloud

Pair a device to start a remote session

bridge idle · waiting for a paired device…