Ports.

How it works

The agent on the box watches for listening TCP ports. When one appears, the daemon on your machine opens the same port on 127.0.0.1 and tunnels it to the box. Servers that bind only to the box's loopback (Vite, most dev servers) are relayed by the agent, and websockets work. On Windows the daemon runs while you are signed in.

npm run dev
# ready on http://localhost:3000
# two seconds later, localhost:3000 works on your machine

Inspect and toggle

An interactive prized ssh session to a non-default box forwards that box's ports for the life of the session.

Limits

• TCP only. UDP is not forwarded.
• Ports 3000 through 9999 are auto-mirrored. The range and per-port allow and never lists live in the config's [ports] section.
• Never mirrored: ports below 1024, port 22, and the agent's port 7377; 5900 is off by default. Anything else outside the range needs an allow-list entry or a manual prized proxy.
• A mirrored port is open to your whole machine, like ssh -L or docker -p 127.0.0.1:; on a machine you share with other accounts, treat it as if the service were running there unprotected.
• Local wins. If something on your machine already listens on a port, the mirror waits, prized proxy refuses it, and an ssh session skips it; nothing binds underneath your own server.
• Every request crosses the network. An app that makes hundreds of database round trips per page should run next to its database on the box, with only the app port mirrored.

A second box

Each box's daemon mirrors that box's ports: a box connected with prized setup --box mango gets prized --box mango ports ls and prized --box mango ports toggle 3000, automatic mirroring included (Several boxes).

Two boxes listening on the same port collide on your machine, so the second mirror shows as conflicted in ports ls; toggle the port off on one box, or add it to [ports].never in that box's config.