how-to · work Open this in the console

Push an agent update.

Updates is how a machine moves to a newer agent. You choose a signed version. The hub never sends an unsigned binary.

Push is a two-step confirm. An offline machine keeps the target and applies it the next time it connects. A proxied device is not in this list. Its proxy is the agent.
01

Open Updates and choose who

The version menu is every signed release this hub is serving. When none is published, the menu only offers clear — on a hub that has releases, they are listed there. To is ticked rows, every machine in view, one company, or a group and everything under it. Push asks you to confirm. Each online machine then fetches that release, checks the signature, and restarts onto the new binary. A row's own button does one machine. Offline says set: the target is stored and applied at the next hello.

Updates page with the roll-out bar and the two Example Co machines
No signed release is published here, so the version menu offers clear. To is who receives it. These machines are offline, so a row says set.

Hub address, above the roll-out bar, is for company admins. See which address a machine connects through is that panel: the name each machine last reported, and re-point for online machines still on an old name.