Updating Murage
How Murage checks for updates, how to install one, how version numbers work, where to read release notes and what's new, and how to go back.
Murage tells you when an update is ready. You choose when to download it and when to install it.
How update checks work
Murage checks the public Murage releases page on GitHub in the background. Nothing about you or your work is sent with the check. You can also check yourself:
- Settings → General → Updates: choose Check for updates.
- The Murage icon in the menu bar or system tray: choose Check for updates.
The Updates card tells you which version you're running and what it found, for example "You're on the latest version we know of", "0.1.60 available" or "Downloading 40%".
Install an update
Mac, Windows and the Ubuntu AppImage
- When an update is available, choose Download.
- When it says the update is ready, choose Restart to update (or Restart and install).
- Murage closes, replaces itself and opens again.
Choose Later to keep working. The update waits until you restart.
Ubuntu .deb
Murage downloads and checks the package, copies the install command and opens a terminal. The card says the update is ready to finish in a terminal. Paste the command, press Enter, and reopen Murage. Murage never asks for your administrator password itself.
Before an update: backups
If you use backups, Murage may take a backup before it updates. The card then says the update is waiting for the pre-upgrade backup. Check Settings → Backups if it needs your attention.
It's a good habit to have a recent backup before any update. See Backups and export.
Version numbers
Murage versions have three numbers, such as 0.1.60. A higher number is newer. While the first number is 0, changes can be large between versions, so read the release notes.
Your version is shown in Settings → General, in the Updates card.
What's new and release notes
- What's new opens once after each update to show the highlights. You can open it again from the + menu or Tools.
- The full release notes are on the releases page and in the changelog.
Each release is built from one exact commit for every platform, and every file is checked before it's published.
Is the update genuine?
- Mac builds are signed and notarized by Apple. Windows builds are signed.
- Ubuntu packages come with a
SHA256SUMS-ubuntu-x64.txtchecksum file. See Ubuntu notes. - Only install Murage from the official download page or the releases page. Never install an update file someone sends you in a chat or email.
Engines update separately
Claude Code, Codex and other engines are separate programs with their own updates. Murage's update doesn't change them. If an engine starts failing after it updates itself, see Troubleshooting engines.
Going back to an older version
Older versions stay on the releases page. Before going back:
- Take a backup.
- Read the release notes of the version you're leaving. Some updates upgrade stored data in a way older versions can't read, and the notes say how to handle it.
- Install the older version over the current one.
If Murage refuses to start after going back, reinstall the newer version. Your data isn't deleted by either install.