Plan a whole-system update
Check the latest product version from the changelog view. Read the release notes and review an ordered, drain-safe update plan with blockers and a dry run before you confirm. Choose where images come from: GitHub, a build on your operator machine or a build on a selected Host.
GitHub is offered as an image source only when the release images exist. Image-only and restarting toolchain rebuilds never upgrade a remote Host agent implicitly; sessions on an older Host keep running with a clear message. An update does not restore a stale database or replay unknown effects. The existing walkthrough does not show this screen; a new native recording is pending.
How it works
Review the plan before it runs
System update lists the release notes, blockers and ordered steps for Core, every Host and the controller database. Run a dry run first, then confirm the update.
Roll back failed steps
Each versioned migration step has an applied check and a required rollback, or an explicit reason why it cannot be reversed. Failed steps roll back in reverse order.
Choose the image source
Use GitHub images when they exist, build on the operator machine, or build on a selected Host and replace containers with its verified image IDs.
Try the interface
Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.
Put your server to work.
Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.