Murage tells you when an update is ready; installing it is your choice. Here’s what each release brought, from its release notes. Counts and names below are as shipped at the time.
Open source. macOS, Windows and Linux.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Search the docs, videos, blog, apps, teams, skills and release notes.
36 releases between September 6 and November 9, 2026.
Murage 1.0.18 is out for Mac, Windows and Linux, led by No limits: when you start the request yourself, your bot gets on with the job, and Murage keeps a short list of files and places protected.
No limits, with a protected list
Set a bot to No limits, ask it for something, and it runs the job. Murage protects certain files and places, such as the keys and sign-ins you have given it, and answers a request for one of them with a clear refusal that says why. Every other level and every other kind of turn works as before.
If a bot has taken in something from outside, such as a web page, an email or a file someone sent, only that bot keeps the extra check. Your other bots keep going without it. Don't put a bot on No limits if it can reach customers, money or other people's data.
Commands that run in your Mac temp folders work as they always should at No limits, while the real system folders stay protected. A command pointed at a folder that is not valid gets a clear refusal at every level.
Writing output to /dev/null works.
New
Today, two ways. The Today page has a Calm view for a short summary and a Detailed view for the full list, in every language.
Approve in one tap. Answer a waiting request right inside Needs you, or Approve all for the stack. A refusal still shows its reason.
Bots read your other chats. A bot can read from your other chats, and you pick the exact excerpts it shares into a room. A bot can also post in a room by a rule you set, and you see each post.
Murage 1.0.17 is out for Mac, Windows and Linux, led by Approve all: answer a stack of waiting requests in one go, while the big steps still wait for you.
Approve all
Needs you has an Approve all button. It shows what you are about to approve, up to 25 at a time, and each one runs once, as if you tapped Allow once.
Payments, email, publishing, deleting outside a bot's folder and other big steps stay in your Inbox for you to answer one by one.
Find things faster
Settings search takes you straight to the setting, opens any folded section around it, and offers to ask your Chief of Staff when nothing matches.
In the help panel, Ask about this screen puts your question into your Chief of Staff's chat.
Today, Needs you and Health each open their own help page.
Buttons show a short tip when you point at them or reach them with the keyboard, and a new hint shows once.
Look and feel
Murage 1.0.16 is out for Mac, Windows and Linux, led by a Health page that tells you what to fix first and a Needs you list you can answer in place.
Health shows what to fix first
Health lists what needs your attention in order, Flux and Fuigo first, with one button to fix each and a way to check again.
Answer right where you are
Rows in Needs you open in place, so you can answer a bot without leaving the list.
Every bot replies the same way: the answer first, one question at a time, in plain words and your language.
A team lead bot can now set up a new section for a client.
Engines
Bundled Fuigo moves to 1.0.39.
Pi tells you when a session is slow to start, and shows what it costs.
Murage 1.0.15 is out for Mac, Windows and Linux, led by new bots starting on Fuigo and one place to answer a bot that needs you.
New bots start on Fuigo
A new bot you have not picked an engine for starts on Fuigo when Fuigo can answer, and otherwise on the engine Murage found on this computer, so your first chat gets a reply.
If Fuigo goes quiet partway through an answer, Murage ends that turn and tells you right away, so you can send it again.
Answer in one place
A bot waiting on you shows one line in the chat. Answer it in the panel above the box, or from the bar on your phone.
Messages waiting for the next turn fold to one tidy line each.
Less in your way
All chats has Back and a close button at the top right, like every other page.
Esc closes the menu or panel in front first. Health closes with Back, its close button or Esc.
Murage 1.0.14 is out for Mac, Windows and Linux, led by one-button engine sign-in and Fuigo 1.0.38.
Sign in with one button
Signing in to an engine is one button in Settings. No terminal and no commands to copy.
Ask Ember in chat on your computer to sign you in and it gives you that same button.
While Murage is still checking a sign-in, Health and Today say "Checking sign-in" until it knows.
Needs you only asks you to sign in to engines your bots or routines use, and first run sets you up on Fuigo and Flux.
Voice notes
A bot's voice note now plays on your phone and in the browser, as well as on your computer.
A voice note or file a bot sends partway through a turn now sits in its reply, not inside Worked for.
Fuigo 1.0.38
Murage 1.0.13 is out for Mac, Windows and Linux, led by a review step before a bot gets more access and a new Health page for your engines.
Review before more access
Raising a bot to Full access or No limits shows you the change to review first.
New
Health page. A new Health page shows each engine's state. Its title and back button stay on screen as you scroll.
Better
No limits asks far less often. Your deny rules and wipe list still apply, and Codex edits and read-only PowerShell commands run under it.
Question cards wait for your answer, and the bot that asked picks the conversation back up when you reply.
Engines remember your setup answers and keep their settings across restarts.
Claude chats on Windows pick up where they left off.
Murage 1.0.12 is out for Mac, Windows and Linux, led by help on every screen and a start that clears deleted chats in the background.
Help on every screen
Press the ? key or the ? button and a help panel opens with tips and search, in every window.
New
Find anything in Settings. Type in the Settings search box and the matching cards appear. The command palette searches Settings too.
Update progress you can read. Starting with the next update, a small box at the bottom left shows the status and percent while a download runs. Escape closes it.
Phone previews in Settings. Settings has a Preview card under Phone and other devices with two switches, phone tools and share and ask. Both start off.
Better
Murage opens first and finishes clearing deleted chats in the background after it is up.
If a start takes longer than usual, the recovery window says so and offers Retry startup.
Murage 1.0.11 is out for Mac, Windows and Linux, led by approval cards that stay open until you answer or the turn stops, and engines that follow your picks.
Your answer is always welcome
A tool approval card in a chat now stays open until you answer or the turn stops, on every engine.
A card that closes without your answer reads Not answered, so the record shows what you actually decided.
New
Sign in with Flux is on by default. It is ready in Models & engines.
File patches are read for what they change. When Fuigo applies a patch, your level applies to what the patch really does. A patch Murage cannot read in full asks first, at every level including No limits.
Grok starts on the model you picked. Murage sets the model once, waits for Grok's own model list when it is still loading, and leaves a session that already runs your pick alone. Stop is honored at every step.
Better
A routine's result lands in the chat it was made in, as one card with the reply, the files and Open run. You can switch this to the Routines list in the routine editor.
Murage 1.0.10 is out for Mac, Windows and Linux, led by bots that get on with the work you trust them with.
Your level means it
At No limits and Full access, your bots run their routines and your own direct messages at the level you chose, without stopping to ask.
Better
Routines keep the level you chose, and so do the bots they hand work to and the follow-up turns they wake.
Direct messages you send your bot from your own Telegram, Slack or Discord count as you, so they run at the bot's level. You can turn this off in Settings.
Long file writes run straight through at No limits and Full access.
Connected apps hold steady on a patchy connection: Murage tries again before it calls them out of reach, so your routines keep their apps.
No limits still stops for the short never-list, such as erasing a disk, and before a bot reads a key file.
How to update
Murage 1.0.9 is out for Mac, Windows and Linux, led by tools on OpenAI-compatible engines, bot calls and a phone your bots can use.
Tools on every OpenAI-compatible engine
Connect any OpenAI-compatible engine and your bots use their tools there too, with the same approval cards and the same Stop as every other engine.
New
Bot calls. When something needs you, your bot can call your phone. The lock screen only says Murage is calling; answer to hear what it is, or choose Not now. Calls off for today is in Settings, Notifications, Calls.
A phone your bots can use. When you ask, bots can check your calendar and add events, read and add reminders, set alarms and timers, find a contact to start a text or a call, and find things nearby. Each request shows a card on the phone for you to approve.
Share to Murage and Ask Murage. Share links, photos and files from any app straight into a chat with a bot, or ask your bots from anywhere on the phone by voice or with one tap. On Android, Murage can be your assistant app.
Health checks. A Health card in the Inbox and in Settings shows what Murage's checks found, with one short daily summary when something changed. The checks read only health figures, never your conversations or memories.
Bots connect to the services you choose. Ask a bot to use an API and it can build the connection itself and keep the key you give it.
Questions from your tools. When a connected tool needs an answer from you, Claude asks you right in the chat and carries on once you reply.
Murage 1.0.8 is out for Mac, Windows and Linux, with smoother Full access on Windows, a cleaner Stop, and more protection for your computer and your secrets.
Smoother Full access
On Windows at Full access and No limits, everyday commands keep flowing even when Murage's check of your computer's setup is slow or doesn't finish.
Raise your default and Murage offers to apply it to your open conversations too, with a count of how many it will change.
No limits in a project room stays on after Murage restarts.
Stop that lands cleanly
On Linux, Stop now gives sandboxed engines a moment to finish up and tidy away their work, so the next turn picks up right where you left off.
Backups you can count on
If Murage can't save its backup state, it tells you exactly what to check (disk space and permissions), and Return to workspace takes you straight back once it's sorted.
Your computer stays yours
Murage 1.0.7 is out for Mac, Windows and Ubuntu, led by backups that handle years of work.
Back up everything, however much you keep
Back up now handles large, long-lived data and tells you plainly what it skipped and why. Find it in Settings.
Backups now always bring Murage back when they finish, whatever the outcome, and tell you plainly if one needs a second look.
New
Hands-off routines. On No limits, routines and project room work run straight through without stopping to ask.
A new phone layout. A compact header and one tidy message box, with everything else a tap away under +.
Your setup guide by email. On first run, your Chief of Staff offers to email you the getting-set-up guide.
Bots that catch up. Your bots can now catch up on what was said in their projects and groups, so you can ask one what it missed.
Use my Chrome, one Allow per session. Allow once and your bot works in your Chrome for the rest of the session, the profile picker stays easy to use, and Murage for Chrome connects.
Murage 1.0.6 is out for Mac, Windows and Ubuntu, led by Murage for Chrome.
Murage for Chrome is here
Add it from the Chrome Web Store and your bot works beside you in your own browser, on the sites you choose.
Add Murage for Chrome right from Settings.
New
Every chat in one list. Find any conversation in one searchable list, opened from a wider chat pop-up.
Bots that draft, you send. A draft-only bot prepares replies for you to review and send, on every engine and channel. Ticket Triage in the library works this way.
Bots know where they belong. Each bot knows which projects and groups it is part of.
Memories in your own words. What your bots learn from you is anchored to what you said, and Forget clears it the moment you click.
Fuigo starts fast on Windows. Fuigo starts quickly and steadily on Windows, however Murage was installed.
Murage 1.0.5, the 1.0.4 hotfix
Murage 1.0.5 is the hotfix for 1.0.4. It includes everything in 1.0.4.
Bots in 1.0.5
Bots can now clean up files across folders in one command. A delete that names folders in different places, such as /tmp/a and ~/b, or C:\a and D:\b on Windows, gets its answer straight away, so Murage keeps responding while the bot works. It still asks or stops exactly as your access level sets.
Fuigo now starts on Windows from every install, including npm. Install Fuigo with npm, from its own installer, or use the one that ships with Murage, and your bots on Fuigo answer from the first turn.
Full notes: murage.ai/changelog
Murage 1.0.4, the 1.0.3 hotfix
Murage 1.0.4 is the hotfix for 1.0.3. It includes everything in 1.0.3.
Claude in 1.0.4
Claude now asks before phone, web search and site tools. Tapping, typing or swiping on your phone, web search, and publishing a site each show an approval card first, as your access level sets.
Claude on Windows with Git Bash now starts its approval tools reliably. When Git for Windows is installed, Claude's turns reach Murage's approval tools, so Always ask shows its card as it should.
Full notes: murage.ai/changelog
Always ask reads commands before they run, apps get grants you control, approval cards reach your phone and calls, memory and rooms stay quick and private, and Murage comes with Fuigo 1.0.31.
Always ask in 1.0.3
Always ask reads each command before it runs. If the text names your home folder, a system folder, a whole disk or a mounted volume, Murage asks first, at every access level, including Full access and No limits.
It covers more than the shell. The same check reads PowerShell, Command Prompt, Windows Subsystem for Linux, and code run through Python, Node and similar tools.
Raw writes to a disk always ask. Any write to a storage device asks first, whatever the device is called.
Apps and engine settings in 1.0.3
Each app gets only the grants you give it. 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 the bot that runs it. Another bot cannot borrow them.
The settings that decide what an engine may do are protected. A bot cannot change them from inside a turn; you change them in Settings.
Murage's own approval hooks stay Murage's. Bots cannot change them, at any access level, including Full access and No limits.
Memory stays quick on long histories, startup and search stay smooth, routines run while you sleep, and connected apps report what really happened.
Memory stays quick and compact on long histories. Each reply's sources are stored as a small step from the one before, so a long-running thread takes a fraction of the disk, and the first memory check of a resumed conversation is held to about a tenth of a second. The upgrade screen shows every step.
Memories that need you are easy to find. A Needs you block and an Inbox card list the memories waiting for your word, with Keep, Keep all, Later, Edit and Undo.
Quick however much history you have. Startup, the Inbox, search, the sidebar and chat export all stay responsive on very long histories.
Routines run unattended. "Always allow for this routine" holds on later runs, your bot reads its own connected-app results without asking, and each past run has a Delete button.
Connected apps report what really happened. A real email sent or calendar event added through a connected app is recorded as done, approvals read in plain words, and your apps go by their own names.
Group chats pick the right bot to answer. With a Flux key, Murage chooses which bot should reply, within about a second.
A message you stopped stays stopped, a queued message runs once, and deleting a conversation also clears it from the coding engines' own files.
Murage for Chrome reads like the app, with your bot's name and color and plain card headings.
Windows installs and uninstalls cleanly without admin rights.
A quick follow-up to Murage 1.0 that keeps conversations whole and learning on track.
Your bots keep their own replies in view. When a bot's memory changes partway through a conversation, it picks up with your messages and its own replies alike, so it always knows what it said and what you agreed. If a reply relied on something you have since forgotten, the bot sees a short "Reply withheld" line in its place.
Reflection runs on current Claude. Bots that use reflection on Claude now reflect on your conversations as intended, including on the latest Claude Code.
Model names read cleanly. The model list shows names like Claude Haiku 5.5 and Claude Opus 4.1, including Claude Haiku 5.5.
Image handling is up to date. Murage uses the latest image library for previews and thumbnails.
Backups on Windows wait for a slow start. On a busy Windows computer, setting up owner-only backup files now waits longer, so the step completes.
Murage 1.0 is here.
It's a team of AI bots that works on your own computer, led by Ember, your Chief of Staff. Ember plans the work, hands it to the right bot and reports back. Your bots run projects with goals and a board, remember what matters, browse in your own Chrome, take your calls and talk to the apps you already use. And you stay in charge the whole time, from your desk or from your phone.
This is the biggest release we've ever shipped. Here's what's in it.
The headlines
Projects that actually get done. Give a project a purpose, a lead and a goal. The lead turns it into a plan, splits the work into cards on a board and hands them out. You sign off when it's finished.
Murage in your pocket. Pair your phone, answer approvals from the lock screen, call your bots and run your projects from anywhere.
Murage for Chrome, arriving in the Chrome Web Store. Your bots can work in your own signed-in browser, in the tabs you share, and they ask before anything is sent.
Bots that learn from you. Correct a bot once and it keeps the lesson. Every lesson shows up where you can see it, edit it or undo it.
Add any tool by pasting a link. Paste the link a service gives you and Murage works out the rest, sign-in included.
Calls that feel like a conversation. Bots answer sooner, wait while you pause to think, and say "One sec" when they need a moment.
Lighter in the background
Murage uses far less disk and CPU while it sits in the background. This matters most when you have a long history. The Inbox and approvals badge now update only when something changes. An idle Murage writes almost nothing to disk now.
Long conversations
Long conversations keep going, well past where most agents stop. Keep one conversation running for weeks, like a sales thread or a long project, and your bot keeps answering with its memory and everything recent you have worked on together. There is no need to start over.
Bots take on far more work. A bot can now hand thousands of tasks a day to its helpers and keep going, well past the point where most agents stall. Murage also looks after itself better: it sorts out the unexpected on its own and always opens ready to work.
You stay in control
Your approvals hold everywhere. A bot set to Ask now checks with you before it acts on every engine, and before every connected app sends or pays, not only for its own tools. Auto still handles the everyday steps and asks before anything new goes out.
Your conversations stay yours. Your chats, routines and calendar open only for Murage itself and the phone you paired.
Calls hear a no. On a call, "don't" means don't, even when the transcript drops the apostrophe. A yes for the whole call covers lookups and page reads only, never actions.
Chat apps keep you in charge. From Telegram, Slack or Discord you can turn down a computer action straight away. Saying yes to one happens in Murage.
What's new
A What's new page shows the highlights once after you update. Each card takes you straight to what it is about: the Team map, Image generation, Models, or the no activity limit in Settings. It opens once and not again.
Rooms
Bots in a room keep the full conversation. Every member can read its teammates' earlier replies after you add or remove a member or change a setting, so teammates can build on work already done.
A reply that used something you deleted is shown as withheld. When a room reply drew on something you have since deleted or changed, bots see a short note that the reply was withheld instead of its text, and you see "Bots no longer see this reply" under it. The same holds when that reply would come back through memory, through a copy of it in another conversation or through a delegated result.
A pinned note that uses a withheld reply is left out. If you pin a room's notes and later forget a reply they rest on, bots are not given that pinned note. Murage says once in the room that the pinned note uses a reply the bots do not see, so you can unpin it and pin a newer one. Replies made after that stay visible to every teammate.
Forgetting a room's notes forgets only the notes. When you forget a room's notes in Memory, the earlier replies they quoted stay visible to the bots. Only a reply that was made with those notes is withheld.
A reply you chose to forget says so. When you forget a room reply itself, you see "Bots no longer see this reply: you chose to forget it." under it, and bots see that the owner chose to forget it.
Room memory reaches every teammate. Bots can recall the room's notes and memories, including notes just updated by another teammate. Rooms also keep answering with short memories pinned.
Clear guidance for pinned-memory limits. If your pinned memories exceed a bot's model capacity, Murage gives you one plain instruction: unpin some in Memory, or choose a model that takes more context. A goal run that needs the same change explains it on its card.
Please read
Routines now have their own approval level. Choose Ask, Auto, Full access or No limits in the routine editor under Advanced > Approvals for this routine. An unset routine follows its bot's level when it runs, including No limits. The conversation, editor and approval cards all show the level that applies.
A routine that needs you says so straight away. When a routine reaches a question or approval, Murage notifies you immediately and marks the run as "waiting on you".
Connected apps
Connected apps recover from brief network interruptions. Each bot checks its app connections again on its next turn, so connections can resume without restarting Murage.
Routines
Long instructions arrive whole. A routine's instructions can be up to 100,000 characters, and the editor tells you before you go over. Nothing is cut off.
Always allow for this routine. An approval card raised by a routine offers Always allow for this routine, which covers that same command or place for that routine only.
One conversation per routine. Each routine keeps its runs together in one conversation.
Auto handles routine cleanup. Bots can delete files inside their own folders and clean up temporary files under Auto. Stopping other programs still asks for approval.
Please read
Murage is now licensed AGPL-3.0-or-later. Murage as a whole, including every Ferrox Labs change and addition, is now under the GNU Affero General Public License, version 3 or later. If you run a modified copy of Murage as a service for other people, you publish your changes. The OpenMausBot portions that Murage builds on remain under Apache-2.0, and NOTICE keeps their attribution. Releases before 0.1.59 remain available under Apache-2.0.
Full access now stops at a few lines. A bot on Full access still does ordinary work without asking, but it now stops and asks before deleting anything outside its own folder, before paying for anything, and before messaging someone for the first time or posting in public. If you want the old behavior, choose the new No limits level (see Approvals).
What's new
What's new. After updating, Murage shows what changed once, with a Show me button for each feature. Reopen it any time from the Help menu.
Tray
Tray. The menu-bar icon now shows the Murage glyph and a count of what needs you. Its menu lists approvals (ordinary ones can be allowed or denied right there), what your bots are working on, and New message to a bot.
Skills
Skills live in Settings. Settings > Skills is one place for every skill: search first, then Your skills, then the library by search or by topic (one Topic dropdown beside the search box). Open any skill to read it in plain form and switch it on for a bot.
Import a skill. Drop or choose a file, a folder or a zip, or paste a GitHub link, right inside Settings > Skills.
What's Changed
Other changes
More reliable desktop startup and updates. By @FerroxLabs in https://github.com/FerroxLabs/murage/pull/6
Same release notes as Murage 0.1.58.
Read the full releasePlease read
Your API key follows your chosen provider. When you change providers on the OpenAI-compatible engine, Murage keeps the new provider address through engine on/off changes and changes to an engine's command-line location. Your new key goes to that provider. Existing settings with an outdated address are corrected when loaded. Connections with their own key remain unchanged.
Windows: set up scheduled backups. Choose a destination and recovery key to complete setup. If an earlier setup attempt did not finish, choose them again. Existing schedules remain unchanged.
Bots and teams
Every bot is itself, everywhere. Each bot brings its own notebook and its team's shared instructions to direct chats, handed-over work, routines and channels. Team instructions you edit reach the bots that use them. In a channel, each bot keeps access to its own memory, its team's memory and the channel's memory. A bot changes its notebook only when you ask it to remember, forget or correct something; routines read it without changing it.
New Team, right in the + menu. The + menu names what each item makes: New Bot, New Bot from Template, New Team and New Channel, with Export bots and Archived bots below. Create a team in one step with its name, bots, optional lead and team instructions. Teams use the same name throughout Murage, including "Move to team…" in a bot's menu.
Talk to Moss, get Moss. In a channel, "Moss, can you…" reaches Moss with or without the @. Bots are instructed to speak as themselves, and messages addressed to another bot stay with that bot rather than going to the Chief of Staff.
The right face on every message. Channel replies show the responding bot's own avatar and name, including teammates answering handed-over work who are not channel members.
A new channel task starts unlocked. Choose New task in a channel and the folder card immediately shows the new task's current state.
Private notes stay private. In a channel or conversation that includes people from Slack, Discord or Telegram, your bots' private notes and team instructions are left out, and only what you have explicitly shared is used.
Bots and teams
Mascot bodies, redrawn. Seven of the ten bodies are now Ferrox Labs' own artwork, built with Blob Studio: Circle, Blob, Capsule, Drop, Star, and the two that were called Shield and Hexagon, now named Cone and Polygon. A body you chose in 0.1.54 stays chosen. The Body picker in Settings → bot → Avatar is one row of ten on a desktop card, two rows on a phone.
Delete archived bots. The Archived panel offers Delete and Delete all with a type-to-confirm dialog. It explains that the bot, its conversations, files, memory and skills are removed, while its channels and their messages remain. Channels continue receiving messages after their lead is deleted, and backups taken after deleting a bot can be restored. If deletion cannot finish, the bot remains whole.
Bots are told what they can do. Each bot gets a short, accurate account of what this install lets it do this turn: its tools, whether it can see images, whether its working folder was checked, that a tool call can pause for your approval, and that a refusal is final. Instructions match each bot's role: a specialist works through its team lead, and a Chief of Staff gets guidance consistent with its own instructions.
Bots can look Murage up. A bot with Murage's tools can answer "how do I do X in Murage?" from Murage's own documentation, offline, with nothing billed. The built-in Concierge profile uses the same lookup.
Models and engines
Engine selector. Each engine appears once with its icon in the model picker and under Settings → Engines.
Model price bands and capability icons. Model rows show published provider rates as a five-step band from $ to $$$$$, with exact per-million rates on hover. Models without published rates are labeled "Price unavailable". Icons identify vision and tool support, and a dated note explains that bands are approximate. Flux Auto shows a range because it selects a model for each turn.
Model list order. The list starts with Flux Router tiers, Auto, Fast, Standard and Reasoning, ordered by cost, then starred models, the engine's models, Flux pinned models and other providers. A Flux tier offered by the engine appears once for that account. If you save several Flux accounts, each account's tiers remain available.
Clear model names. Models display their readable names, such as "Flux Auto". The chat picker lists chat models only, so flux-voice and flux-image are not offered there.
Bots and teams
Mascot bodies. Choose your bot's mascot shape: flame, blob, circle, squircle, capsule, drop, shield, hexagon, diamond or star. You'll find them in Settings → bot → Avatar → Body. Adapted from OpenMausBot.
Drag a bot onto a team in the sidebar to add it. If the team already has a lead, dragging in another lead is refused and nothing changes.
Team instructions can now be edited after the team is created: use the book icon on the team's sidebar header.
Pin tasks to the top of the task switcher.
Easier to spot the open conversation: the selected sidebar row now has a gold edge.
Avatars: drop an image straight onto the avatar to upload it. The Circle, Rounded and Square shapes now show on mascots too, including on the Team map.
Images
Reference images for Fuigo. Bots running on Fuigo receive attached images and reference images.
Clearer image-request feedback. When an image provider declines a request, you see its error code and message.
Claude conversations now handle automatic retries and follow-up messages after Stop more reliably. These three changes apply on macOS, Windows and Linux. The bundled Fuigo engine is unchanged.
Improved
Save, Restore and queued messages continue after a Claude retry. When Claude automatically retries starting a request, Murage tracks it through completion, releases the workspace for Save and Restore, and delivers channel messages waiting behind it, including Telegram and Discord messages.
Send your next message after Stop. A new message waits briefly for Claude to finish stopping, then starts. A message sent while a turn is still running and has not been stopped is still declined, as before.
Follow-up messages keep their place after Stop. You can send a new message or edit and resend immediately after stopping. Murage keeps the new run's selected provider, usage, reply and unread status separate from the previous run as it finishes closing.
Unchanged from 0.1.52
Everything in the 0.1.52 notes still applies, including the open items listed there. Returning to 0.1.51 after running 0.1.52 or 0.1.53 is not supported, because the saved-files storage differs.
Every bot gets a workspace you can see and edit beside the chat. Bots can ask you a question and receive your answer through answer cards, local models have their own setup, and connected apps move onto your Flux Router account. Images, audio and video are checked before they are shown, including saved-file cards that show the file right in the chat. The engine runtime, desktop app, companion, installer and hosted broker each received a set of audit-driven improvements. Stop works on every engine, and all seven language packs are complete.
Added
A workspace pane beside the chat. Browse the conversation's files in a resizable pane that remembers its width, with at least 360 px for chat and 320 px for the pane. Narrow screens get Back to chat, and Expand gives files more room. Tabs identify the file and its location. Preview Markdown, protected HTML, plain text and images, or open or download other files. One click reuses an unedited preview tab; Keep open or Edit keeps the tab available. Unsaved tabs stay in place and ask before closing. Actions include Save, Save a copy, Save this version, Download, Open in app, Show in folder and Open in Files.
A Markdown editor that only writes on Save. Files open in rich editing when their exact formatting can be preserved; other files open as their original text in Source mode. Reloading keeps the file unchanged. If a bot changes the file while you edit, Murage shows both versions and lets you choose Use the disk version or Keep my version. If a bot turn is using the folder when you save, Murage tells you in plain words and nothing is written. The version you replace is retained in Files first. Up to 50 unsaved drafts, totalling 10 MiB, can be recovered after an unexpected app close. Drafts are clearly distinguished from saved files, and a recovered draft waits for your choice if you have already started typing.
Files brings working files and saved copies together. Browse the conversation's current working folder with breadcrumbs, folders loaded as you open them, name search and 200 entries per page. Search tells you when its results are incomplete. Every row is labeled Workspace file or Saved copy. Conversations without a workspace and remote runs say so, rather than listing your home folder. Open in app and Show in folder check the selected file and allowed file type before handing it to your computer.
Bot outputs are saved automatically. Files written to a task's managed outputs folder become verified saved copies with the producing bot and run identified, plus a card in the chat. This covers ordinary files up to 25 MiB, with up to 20 saved per turn. An unsuccessful or canceled turn retains its output records without publishing saved-file cards. Generated image data is retained before attachment, so an interrupted publication can resume after restart without another provider request or a duplicate message.
Saved-file cards show the file itself. Images appear in the chat and open in the lightbox. Audio and video use embedded players, with one playing at a time and no autoplay. Markdown, text and code initially show 2 KB, expandable to 256 KB. HTML uses a protected preview, while PDFs and other binary files keep their buttons. Open here opens the working file in the workspace pane. Source code and configuration files can preview as text; SVG images, credential files, archives and binary files remain download-only. Access is checked before file content is delivered.
Answer your bot in a question card. Claude Code, Codex, Fuigo, ACP engines and Pi can show questions with descriptions, options, multiple selections, Other and free text. Use the keyboard with 1 to 9, Tab, Enter and Esc; shortcuts are listed in the Send button's tooltip. Questions require your own answer and cannot use Always allow or automatic review. Skip reaches the engine immediately. After 30 minutes, the card shows Expired and offers Send as a message for a later answer. Cards survive restarts. Links open only when you choose them. Each question has its own section, selected options are highlighted, and completed cards retain your choices with an "Answered · time" footer.
Questions on Telegram. Your paired Telegram account receives each question with numbered option buttons, multiple selections with Submit, Reply with text and Skip. Answers are checked against the current question and your paired account. Questions asking for secrets stay inside the app.
Local models have their own setup. Settings → Models shows the addresses checked for Ollama, LM Studio, llama.cpp, vLLM and SGLang. Add, edit or remove servers on your computer, home network or tailnet using HTTP, or use HTTPS elsewhere. Saved keys stay hidden. Check each model's tool support and see a plain result with expandable details. Murage reads the server's loaded context size, and Ollama offers Create a 64K copy. Fuigo, Pi, OpenCode, Qwen Code, Hermes, Droid and Kimi can use a checked model; Codex and Claude Code appear once their compatibility checks pass. The picker shows model and server together and identifies models that do not pass the tool check.
Your assistants can keep working together. Two assistants can run side by side, and access to this computer is coordinated only when a bot actually performs a computer action.
Assistants can work in their separate private workspaces at the same time, including when supported Auto/local desktop tools are available.
Each default browser profile is managed independently.
Host computer access is coordinated when a computer action is requested, with scoped access for each active conversation.
Stopping one assistant revokes its access without stopping another assistant's work.
All features introduced in 0.1.50 remain available. This is a focused concurrency update.
Investigation continues into reported engine interruptions and an occasional Mac shutdown delay while credentials are being saved. These remain open in this release.
More useful first steps, clearer ways to catch up on work, and better control over your bots. This release brings together onboarding, a persistent Inbox, saved Files, managed memory, independent conversations and native engine updates, alongside important reliability fixes.
What's new
A clearer first run. Choose what you want help with, select an engine and review a small starter team. Interrupted setup can resume without duplicating your workspace.
A persistent Inbox. Return to results and decisions after a desktop notification disappears, with links back to the relevant work.
Files and reports in one place. Find saved deliverables, preview supported files and download them. Reports link to their original conversation, and registered files survive app restart.
Searchable managed memory. Bring existing notebooks into memory and use remembered information across engines while preserving original notes and controlling who can access them.
Independent conversation threads. Keep task-specific controls and cancellation separate while sharing a bot's identity and skills.
Better bot and team exports. Contextual selection, accurate role descriptions and a separate conversation Markdown export make it clearer what you are sharing.
Cleaner navigation and settings. A visible Tools menu, sectioned bot settings, separated engines/models/connections and consolidated model controls reduce setup confusion.
One Flux Router connection. Manage your Flux Router key in one place and choose the connection you want to use.
More reliable Windows installation and startup. Fuigo 1.0.8 remains bundled, so desktop users can start without installing Node.js, npm or Fuigo separately.
Windows can read and run Murage's installed application files while keeping them protected from changes by the app's restricted components.
Windows upgrades use a shorter temporary folder path and restore the normal launch settings afterwards.
Murage can recognize when a previous session has ended, using available startup records to determine whether the installation is still in use.
Murage clearly identifies an installation recorded as belonging to another computer.
Upgrades and normal uninstall procedures retain existing conversations and settings. If an installation is recorded as belonging to another computer, Murage explains that status and preserves the record; displaying it does not unlock or recover the installation.
Investigation continues into reported engine and Fuigo interruptions. Those reports remain open in this release.
Murage 0.1.48 makes memory, team coordination and model setup easier to use.
Local memory captures and recalls by default for new profiles. Existing Off/Paused choices are preserved. Import existing Markdown notebooks and review, correct, share or forget stored memories.
Chiefs can inspect and manage their organization, delegate through team leads and specialists, and track bounded handoffs. Permission requests and scoped access are visible.
Models and Engines have separate settings. Add named provider connections, browse compatible chat models, and route supported engines through Flux or your chosen provider account.
Unified browser controls let you watch live and take control, with access tied to the relevant work.
Bots with compatible tool support can request image generation with your approval, using supported connected providers and GPT Image 2 through Flux by default.
Clearer setup, engine-update actions, customer-facing error details, Telegram connection recovery, Blank Bot/From Template choices, and descriptions for all 66 teams.
Smart Trader setup guidance includes TV Control 2.5.1. Fuigo 1.0.8 is bundled.
Slack, Discord and WhatsApp are not part of this release. Existing profiles retain their settings; this update leaves remote memory processing and cross-project sharing off unless separately enabled.
Desktop downloads and checksums are attached below.
Adds opt-in managed local memory with scoped access and owner controls to review, correct, share, pin and forget records.
Keeps memory's original source history with your installation, supports rebuilding its search information, and includes memory in recovery and deletion handling.
Updates the bundled Fuigo engine to 1.0.7.
Includes improvements to the desktop app, recovery, engine and bot-role handling, and Telegram.
Managed memory supports everyday conversations. Processing large volumes of material and sustained intensive searching remain outside its current scope. Memory keeps each bot's existing file-access and delegation permissions.
Windows installers are signed. Apple Silicon and Intel Mac downloads are signed, notarized and stapled. Ubuntu installation and upgrade checks were completed, and the complete installer set and update-file hashes were verified.
Intel Mac memory support
Intel Macs support keyword memory, owner controls and source recovery. Local semantic memory is available on Apple Silicon, Windows x64 and Linux x64; its model downloads are limited to those supported systems.
Known UI issue
On Linux, longer bot names may appear shortened with an ellipsis in the sidebar. Use the accessible name or rename control to read the full name. Stored names and memory retrieval remain unchanged.
Downloads
macOS Apple Silicon: Murage.dmg
macOS Intel: Murage-intel.dmg
Windows x64: Murage-setup.exe
Ubuntu x64: Murage-amd64.deb or Murage.AppImage
macOS packages are signed and notarized. Windows packages and the bundled Fuigo executable are signed. Versioned files and updater metadata are included alongside the stable download names.
Reliability and security
Tool access and approvals stay tied to the work they authorize.
Diagnostic reports remove more sensitive information and limit how much log data is read.
More reliable installation, shutdown and updates on Linux.