Connect your computers

How your machines are found

PAVONA uses Tailscale to see the machines on your private network. The panel's Machines screen (and /peers in the console) lists every machine on your tailnet and whether it is online. That information is read from tailscale status, and there is no hand-kept list behind it. Machines that can hold models are probed for runtimes, and a peer that answers can serve models to this install. Without Tailscale, the fleet is this machine only, 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

You can attach a file that is on another machine, with /attach in the console or the attach control in the panel. By default it is read by reference, over the tailnet, with SMB: PAVONA 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, for example), the attach says so. You can ask for a copy when you want one.

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

Watching the agent work

While an agent is reading files or 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. Turn it on 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. An unattended update installs only a release that has passed the release checks.