Your machines, measured

PriestAI uses Tailscale's own view of your private network. The panel's Machines screen (and /peers in the console) lists every machine on your tailnet and whether it is online — read from tailscale status itself, not from a hand-kept list. Machines that can hold models are probed for runtimes; a peer that answers can serve models to this install. No Tailscale? Then the fleet is this machine, and the probe says so.

Models on other machines

A model served by another machine of yours is used like a local one: name it, and the resolver finds it by probing your machines. The Models screen shows which machine holds what, and /seats in the console shows which model is assigned to each role and what each one measured.

Files read in place

Attach a file that lives on another machine — /attach in the console, the attach control in the panel — and by default it is read by reference, over the tailnet, with SMB: PriestAI reads its contents over the network without maintaining a separate attachment copy. The source file stays on the other machine. If a machine cannot be reached over SMB (a phone, say), the attach says so; you can ask for a copy when you want one.

/browse <host> lists a directory on a peer over SMB — read-only, always. Browsing is how you find the path to attach; it is not a file manager, and it never writes.

Watching the agent work

When an agent works — reading files, running commands — you can watch what it is looking at in a small picture-in-picture window that you can move and resize. It is off by default, enabled per account in the panel's Settings (under The agent's window), or from the console with /toolview. The window is the panel showing the agent's tool view as it works; if the panel is not running, the console says so instead of opening an empty window.

Updates across your machines

Each install updates itself through the same verified path: the release is checked against its published hash before it installs, and the panel restores the previous build by itself if the new one fails to start. The console's /update uses the same path. Nothing updates unattended that has not passed the release checks.