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 always see each other's replies. Every member of a room now reads what its teammates said there, also after you add or remove a member or change a setting. Before, a change like that could hide earlier replies from the bots, so a teammate would redo work that was 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 no longer given that pinned note. Murage says once in the room that the pinned note uses a reply the bots no longer 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 recall reaches every bot in the room, and a small pin no longer stops the room. Bots in a room now bring back the room's notes and what they remember, also when a teammate's reply has just updated those notes. Pinning a short memory no longer makes every bot in the room fail to answer.
One plain line when a turn is refused. If your pinned memories are too long for a bot's model, Murage says so once, in plain words, with what to do: unpin some in Memory, or choose a model that takes more context. A goal run refused for the same reason shows why on its card.
Rooms with long histories keep working. A room with a very long history no longer stops answering.
Messages Murage cannot confirm stay outside your memory. A room message whose sender Murage cannot confirm no longer gives bots what they remember about you, your preferences or your teams, and the same goes for the handoffs it starts.
Each teammate gets its turn. A handoff to a teammate starts right after that teammate's own room reply, instead of after the whole round, and a teammate that is still waiting for its turn keeps its place.
Murage says when a bot could not answer. When a bot in a room could not answer or stopped part way, Murage says so in its own line with the reason, so it never reads as the bot's own words.
Room replies keep going while a bot is working. A room reply no longer stops at a fixed five minutes. It stops only after the set number of minutes with no activity (20 by default), or when you press Stop.
A bot that cannot start its turn frees the room. If a bot cannot start its turn in a room, the room is freed and a plain line says so, instead of staying busy.
Teams and tools
Bots on Fuigo can reach their teammates again. A bot that runs on Fuigo can now ask a teammate, hand work off and use Murage's own tools, in a room and in a direct chat. Before, those calls failed, so a lead on Fuigo ended up doing the work alone.
Every engine gets tool names it can call. The names of Murage's tools in what bots read, including image tools and error lines, now match the engine each bot runs on, so a bot no longer gets "Tool not found" when it follows them.
Image generation
Every saved image-capable key appears in Image generation. A key you saved under Settings → Models for a provider that makes images now also shows in Image generation, including xAI keys and keys saved with a slash at the end of their address.
Your Google Gemini key works for chat and images. Add a Google Gemini key under Settings → Models and bots can chat on Gemini models, and Image generation can use it too. A key saved under the wrong provider is never sent to another one; Settings shows it for you to review.
Sending more than 10 images no longer fails the turn. The first 10 go to the bot, and one plain line says how many were not sent. The message box tells you before you send.
Image generation takes longer prompts and more shapes. Each image model now has its own prompt length, so a model that takes a long, detailed prompt gets all of it. You can ask for portrait and landscape shapes such as 9:16, and the approval card shows the prompt length, the model and the size that will be made. When a model cannot make what you asked, Murage says so before anything is sent.
Images that take a while are never cut off. An image you approved keeps going until it is finished, however long the model takes. If nobody answers the approval card, the bot is told plainly that the card closed and nothing was sent.
Your image library stays yours. Your saved image styles and reference packs are used only when you talk with your bots, not when someone else messages them.
Saved prompt blocks. Save a part of an image prompt you use again, such as a character or a brand look, as a named block. Bots send saved blocks first, then the scene. Every save is a new version, and earlier images keep the version they used. You and your bots can add them: find them under Settings → Tools & Connections → Image generation.
Reference packs. A bot can save up to 16 reference images from a conversation as a named pack and use the pack again later. Murage checks each image against its saved copy every time the pack is used.
More control over each image. Where the model supports it, bots can ask for several images at once, PNG, JPEG or WebP, a seed, a transparent background, or an exact size in pixels.
Long renders are followed to the end. For models that send their images in parts or work as a longer job, Murage follows the render until it is done, and a render that was interrupted picks up where it was instead of starting again.
See what each model can do. Image generation in Settings shows each model's prompt length and sizes, when it last worked, and a Check this model now button. A daily check of the default model is off unless you turn it on.
A bot that leaves out a detail an image needs is told what to add. When a bot asks for an image without a detail the request needs, it gets one plain line saying what to send, so it gets it right on the next try.
Clearer cards and lines. The approval card names the connection the way Settings does, and when a model sends back no image, Murage says why. The line under a generated image names the provider as Settings does, for example "through Flux Router".
Long work
A working bot is never stopped by a fixed clock. A turn that is still working stops only when it goes quiet for the time you set, when you press Stop, or when it reaches a budget you set. This holds on every engine, including Antigravity and Box.
Bots on OpenAI-compatible engines, MiniMax and xAI wait for slow answers. A model that takes a while to answer is no longer cut off after two or three minutes of waiting.
Long commands on a bot's computer run to the end. A command that takes a long time keeps running as long as it shows activity, and stops when it finishes, goes quiet, or you press Stop.
Clear stop lines. When a turn does stop, the line in the chat says what happened in plain words, without setting names or internal codes.
Languages
Translations are up to date and load when you pick them. The seven translated languages cover the newest screens, and each one loads only when you choose it, so Murage opens faster.
Mac
The first-run step bar clears the window buttons. On a Mac, the steps across the top of the first run no longer sit under the close, minimize and zoom buttons.
Backups
Your pre-update backup choice is kept. If you tick "Back up before installing an in-app update" under Advanced before you first turn on backups, that choice is now kept. Where this install cannot take a backup before an update, setup tells you so.
Your recovery key stays out of folders that sync to the cloud. When Murage chooses where to save your backup recovery key, it no longer uses a folder that syncs to OneDrive, iCloud Drive, Dropbox or Google Drive, and it starts with your home folder instead of Documents. If you pick a folder that syncs, Murage tells you and asks before it saves anything there.
A recovery key already in a folder that syncs is pointed out once. If an earlier version saved your recovery key in a folder that syncs to the cloud, the Backups page tells you once and offers Move and Keep here. Move puts a checked copy in your home folder, points your daily backups at it and then removes the old file. The cloud service may still keep the old file in its recycle bin, so Murage reminds you to empty it there. If Move cannot finish, Murage tells you what happened and what to do next.
The off-site password file follows the recovery key's rule. The password file for off-site backups is saved in your home folder, never in a folder that syncs to the cloud, and Murage asks first if you pick one that does.