Understand TermSquad and Software Updates

Different parts of a TermSquad computer have different update paths. Identify the component before choosing an update action.

Which software are you updating?

Component	Update path
TermSquad’s managed runtime	Managed platform delivery and recovery.
Herdr	Automatic updates and eligible rollback in Settings.
Installed AI tools	Settings → AI tools → Update tools, when offered.
Ubuntu system packages	Ubuntu security maintenance and deliberate admin package management.
Project dependencies	The project’s package manager and version policy.

Updating one component does not imply that every other component is current. For example, refreshing a model catalog does not update an AI CLI binary.

Before changing software

Save work and read the operation’s message. For a project dependency update, review its lockfile changes and run the relevant tests. For a system package change, use the admin account and review what will be installed.

Some changes require a fresh process or restart before they take effect. A browser refresh is not a computer reboot.

Check an update problem

Record which component failed, its visible version, the time, and the error. Avoid mixing a tool reinstall, Herdr rollback, and computer reset in one troubleshooting attempt.

The app’s controls and reported state are the best guide to what is supported on that computer. Older machines may need a managed runtime update before a newer dashboard capability becomes available.

Read Update Installed AI Tools, Manage Herdr Automatic Updates, and stuck operations.