Mount.

Mount is experimental. The command works end to end, but a dropped connection unmounts rather than reconnecting, and details may change.

The model

prized mount

wakes the box if it sleeps, mounts its home directory at ~/Prized/boxes/<box>, and opens the folder in Finder. Everything you see is served live from the box: no sync, no local copy, no disk used. Press Ctrl-C in the terminal to unmount.

It mounts as a real volume, so it also appears in the Finder sidebar under Locations, named <box>.localhost. Ejecting it there unmounts and exits the command, the same as Ctrl-C.

Mount and sync answer different questions:

A synced project is a mirrored folder pair that costs local disk and covers one project. A mount is a live window over the whole box that costs nothing locally, at the price of a network round trip per uncached operation. Browsing folders, Quick Look, editing a file, and dragging files out all feel fine; running builds or git status on a large repo against a mount does not. Keep working sets in sync, and reach for mount when you need to see everything.

Usage

prized mount              # the configured box
prized mount mango        # any box on your account
prized mount --dir /var/log --read-only

The command stays in the foreground while the volume is mounted. Ctrl-C unmounts and exits; closing the terminal does the same.

How it works

The mount is the stock macOS NFS client pointed at a server the CLI runs on 127.0.0.1, whose backend is an SFTP session to the box over the same tunnel prized ssh uses. Nothing kernel-side is installed and no sudo is needed. File bytes flow straight between Finder and the box; your Mac only ever holds them in memory.

If the box suspends or the connection drops, the volume is unmounted so Finder never hangs on a dead mount. Run prized mount again to remount.

Troubleshooting

"mountpoint is not empty". Something is already at that path, usually a mount left by a previous run. Unmount it and try again:

umount ~/Prized/boxes/<box>

"Operation not permitted" listing the folder in a terminal. macOS gates access to network volumes per application. Finder has that access; your terminal may not. Grant it Full Disk Access in System Settings under Privacy and Security, or use Finder for that folder.