Why doesn’t Muster update itself silently?

Why updates wait for a click

Because Muster is holding live agent sessions and a running queue, and an app that restarts itself would take them with it.

What a silent update would interrupt

At any moment Muster may have several agent sessions mid-edit, a queue with tasks in flight, and acceptance commands running. Restarting to install a new version would kill CLI processes in the middle of writing files.

The damage is not theoretical: an agent interrupted between two edits leaves the repository in a state nobody asked for and nobody reviewed.

What Muster does

Checks at launch and every six hours, downloads in the background, and then says so and waits. The band stays until you dismiss it for that version or restart. The install happens on a restart you chose.

Why you are told at all

Because the alternative was worse. The “update ready” state used to live only in a settings screen, and people who never opened it ran old versions for weeks without knowing. A band that you can dismiss is the compromise: visible once per version, never twice.

What this is not

It is not a kill switch. Muster does not require a server to launch, does not check a licence over the network on every start, and does not stop working because a new version exists. If you never update again, nothing about the copy you have changes — see Updates for what stopping your renewal does and does not do.