Murage 0.1.60 is out for Mac, Windows and Ubuntu. The headline is backups: they now work from start to finish on all three, and you can keep an encrypted copy on your own server. Routines get their own approval level, and a few everyday things got easier.
Here is what changed, in plain words. The full list is in the 0.1.60 release notes.
Backups that finish the job
Everything Murage knows lives on your computer, so a backup is the thing that saves you when a laptop dies. In 0.1.60, Turn on backups does the whole job. Pick a folder, and Murage makes your recovery key, switches daily backups on and takes the first backup straight away.
- Mac, Windows and Linux. Backups and restores work on all three, including Windows standard accounts, names with spaces and roaming profiles.
- Restore onto a new computer. Bring your bots, memory and chats across. Snoozed conversations come too.
- Nothing in a bot's folder stops a backup. Shortcuts, odd file names and rebuildable folders such as
node_modulesare left out, and Murage lists by name what it skipped. - A backup that stops tells you. An Inbox item and a notification say what stopped it and what to do. If a bot is waiting on your answer, Backups names the bot and starts as soon as you answer.
- USB sticks formatted exFAT work as a backup folder. On Windows, a network folder or USB stick is refused with a sentence saying why.
- While Murage is closed. Backups now run with the app closed in the Linux AppImage as well as the
.deb, and on a Mac. Windows still backs up while Murage is open.
An off-site copy on your own server
A backup on the same desk as the computer is lost with it. You can now keep a second encrypted copy on a NAS, a home server or any server you reach over SFTP, as well as S3-compatible storage such as Backblaze B2 or Cloudflare R2.
Murage does the fiddly parts. For SFTP it makes its own key for the server, shows you what to add, and asks you once to confirm the server's identity. It never asks for the server's password. For both SFTP and S3, it creates the backup store and its password itself. Keep a copy of that password somewhere secure; you need it to restore on another computer.
Off-site copies work on Intel Macs, Windows and Linux as well as Apple silicon. Step by step: Backups and export.
Routines at their own level
Each routine now has its own approval level: Ask, Auto, Full access or No limits. Set it in the routine editor under Advanced → Approvals for this routine. A routine you haven't set follows its bot's level when each run starts, so a bot on No limits no longer stops its own routines to ask. Reading your keys always asks.
- A routine that needs you says so. When a run hits a question or an approval, you hear about it at once and the run ends as Waiting on you. Answer, and it carries on.
- Always allow for this routine covers the same command or place for that routine only.
- One conversation per routine. Runs no longer pile up as separate conversations.
- Long instructions arrive whole, up to 100,000 characters.
More in Routines and webhooks.
Narrower yeses
- Always allow this exact command here. A command card now offers the narrowest remembered yes: that exact command, in that folder, on that engine. Anything else still asks.
- The Always allowed list. Each bot lists everything it always allows under Bot settings → Permissions → Always allowed, and you can remove any of it.
- Fewer false stops. Deleting inside a bot's own folders and temporary files no longer counts as dangerous on Auto, and scripts are judged by what they actually delete, not by words in them. The stop line's table tests grew to 112 cases. See how we test.
- Pi asks first. Pi bots now ask Murage before running commands, editing outside their folder or using connected apps, like Claude Code and Codex.
- Only you can say yes. Only your own desktop app and paired devices can answer an approval card.
Snooze, teams and About me
- Snooze. Snooze a conversation for an hour, until tomorrow morning, next week or a time you pick. Anything owed to you, such as an approval or a question, wakes it straight away. Conversations with a question waiting show a badge.
- Manage teams. Rename a team, change its members and its lead, or delete it, from the sidebar or the channel details. Deleting a team never deletes a bot or a conversation. See Teams and team leads.
- About me. Settings → About me holds a short profile of you. Your bots read it on your own turns and never on turns started by other people or webhooks. Each bot's What shapes list has a switch for it.
Smaller things that add up
- Deleting a conversation deletes it everywhere: its messages, files, attachments and the history each engine kept for it.
- Connected apps stay connected. A short network blip no longer cuts your bots off from their apps until a restart.
- A cleaner Inbox. I don't use, Turn it off and Dismiss all take effect straight away.
- Voice picker. Every voice in the list has its own play button.
- Notification sounds can be turned off on this computer.
- Paired devices.
murage deviceslists your paired phones andmurage devices removeunpairs one. - Help inside the app. Ask a bot how Murage works. On most engines it answers from Murage's own help pages.
How to update
If you already have Murage, the app offers the update: look for the update banner, or choose Check for updates from the menu-bar icon. Downloading and installing are always your choice.
New to Murage? Download 0.1.60 for macOS, Windows or Ubuntu. Every installer lists its SHA-256 checksum on the download page.
A few honest limits
- Backing up while Murage is closed isn't available on Windows yet. Backups while it's open work there.
- The built-in browser for each bot is on Mac and Linux, not Windows, in this release.
- Controlling your own computer works on macOS, and on Ubuntu in an Xorg session. Not on Windows.
- Murage runs while your computer is on. Murage Cloud isn't open yet.
Thanks to everyone who sent bug reports and ideas. Keep them coming on GitHub.