Updates
Everything that can update — the app, each device, the driver, your extensions — lives in one list.
Everything that can update does so through one registry, so there is one place to look and one thing to trust: the companion app itself, the firmware on each device, the audio driver, your model and speech providers, your apps and skills, and the runtimes they run on.
You almost never go hunting. The companion checks on its own, and anything pending surfaces where you already are — a dot on the Library, a badge in the menu bar, a card in About.
Where updates live
Two surfaces, one source underneath.
| Surface | What it does |
|---|---|
| Library → Updates | One list of everything pending — the app, firmware per device, the driver, apps, skills. Each row carries its own Update action and a Read full notes. Groups appear only when they have something to install, so the tab stays quiet when you are current. |
| About | The companion updating itself: the available version, Install & relaunch, Check now, and a toggle for automatic checks. |
Bring everything current
Check now
Open About and press Check now, or let the automatic check do it — it is on by default. One check re-asks every updatable at once, not just the app.
Review what's pending
Go to Library → Updates. Each row shows the version you have, the version available, and a one-line summary. Read full notes opens the complete changelog before you commit to anything.
Apply
Press Update on a row. Installs run one at a time — start a firmware update and the next one waits its turn, so nothing collides. A firmware update streams to the device over the same link you are already connected on, and you can cancel it mid-flight.
Updating the app relaunches it
When you install a companion update, it downloads, then Zeph relaunches itself to finish. Your device reconnects on its own afterward. Every other kind — firmware, driver, apps — updates in place without a relaunch.
When a row asks for permission
The audio driver installs into the system, so bringing it current needs a one-time administrator prompt — the row shows Reinstall instead of Update. Cancelling the prompt is not a failure; the row simply stays as it was, and you can run it again later.
What updates, and where it comes from
One registry, every updatable
Why it's one list and not five
The companion used to keep separate machinery for each kind of update — one path for itself, another for firmware, another for apps and skills. They were consolidated into a single registry: one place that holds the current and available version of every updatable, one subscriber that reacts when something changes, and one queue that applies them in order. That is why Check now covers everything at once, why progress looks the same whether it is a firmware install or the app downloading itself, and why the bundled providers and runtimes appear as a single line instead of sixteen.