Murage 1.0.3 is out for Mac, Windows and Linux. This update is about staying in charge: Murage now reads each command before it runs, your approvals follow you to your phone and your calls, and every app and bot gets only what you hand it. Here is what you can do now, in plain words.
Always ask reads each command first
- Murage asks before a command touches the big places. If a command names your home folder, a system folder, a whole disk or a mounted volume, Murage asks you first. That holds at every access level, Full access and No limits included.
- It reads more than the shell. The same check covers PowerShell, Command Prompt, Windows Subsystem for Linux, and code run through Python, Node and similar tools.
- Raw writes to a disk always ask, whatever the device is called.
- OpenClaw follows your settings. At Ask, OpenClaw asks before it runs anything. At Auto and Full access it follows your own OpenClaw command settings, as in 1.0.2.
Always ask reads a command as it is written. It is a strong first line, and a few command shapes still get past it. The 1.0.3 changelog lists them plainly.
Approvals on your phone and in calls
- Approval cards reach your phone. Allow or deny from the phone and the waiting bot carries on.
- Calls tell you what is waiting. A call says how many approvals are waiting and lets you answer by voice.
- Your draft stays put. The composer keeps what you were typing while an approval card is open.
Each app gets only what you give it
- Grants are per app and per bot. A connected app asks before it reaches a new tool, and what you allow stays with that app and that bot.
- A routine's remembered approvals stay with its own bot. Another bot can't borrow them.
- Engine settings are yours to change. A bot can't change what its engine may do from inside a turn; you change that in Settings.
Memory that knows where it came from
- Recall an earlier thread. Ask a bot to find what was said in another conversation and it reads that thread, within what it is allowed to see. It works with memory off or paused.
- Each memory remembers its conversation. A bot reads only memories from conversations it was part of, and that holds when you switch its engine.
- Quick on very long histories. No long freezes while memory builds, and a forget or an edit cleans up at a steady pace in the background.
Good to know: memory added while a forget or an edit is still being cleaned up appears once that cleanup finishes. Until then a bot answers without it. Small installs finish in seconds; on a large install it can take a few hours. Right after a large delete or forget, a bot's first reply can take about 5 seconds longer while the cleanup keeps its steady pace.
After a memory settings change, an import or a team change, a bot's recent-work list leaves out replies from other conversations that rested on memory shown before the change. Its pinned records, team memory and the room's own lines stay with it.
Teams that follow through
- Hand-offs answer straight away. Delegating to a teammate always brings an answer back to the asking bot, with the teammate's words or a plain line saying what happened.
- Delegating bots follow through after a restart. When a teammate's reply arrives, the asking bot picks up the work, even if Murage restarted in between.
Windows
- Codex sessions start with their approval check connected.
- Short folder names are recognised as inside your project.
- Routines keep running when their skill bundle moves.
Setup and updates
- First-run setup finishes once your first backup has run and checked out. You start with a backup you know works.
- Moving between 1.0.2 and 1.0.3 keeps all your data.
- Fuigo 1.0.31 comes bundled.
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 the latest version for Mac, Windows and Linux. Every installer lists its SHA-256 checksum on the download page.
The full list of changes, including the known limits, is on the changelog.
Thanks to everyone who sent bug reports and ideas. Keep them coming on GitHub.