What Murage can’t do yet.
Here’s what Murage can’t do yet, in one place, so you don’t find it out a week in. Each limit says what to do instead today. Where something is coming, the line says so, with no date.
Checked against Murage 1.0.18 on November 9, 2026. The same list sits on the compare page.
The list.
Today Murage runs while your computer is on and Murage is open. Murage Cloud (coming soon) is your own private virtual server in the EU, encrypted, with its own browser.
The desktop app runs while your computer is on. Murage Cloud (coming soon) is your own private virtual server in the EU, encrypted, with its own browser.
Today, instead: Leave Murage running on a desktop that stays on. If work has to run with your computer off, a hosted product does that today.
An OpenClaw bot keeps OpenClaw’s own tools. Murage’s teammates, memory, connected apps and stop line don’t reach it.
Today, instead: For work that needs Murage’s teammates, memory, connected apps and stop line, run the bot on Fuigo, Claude Code, Codex or Hermes.
Four chat apps: Telegram, Slack, Discord and WhatsApp. No iMessage, Signal or Microsoft Teams.
Today, instead: Reach your Chief of Staff in Telegram, Slack, Discord or WhatsApp. Bots can still read and post in other messaging apps you connect, such as Microsoft Teams.
No phone calls to outside numbers. Voice calls with your bots happen in the app.
Spend limits are set per project, in minutes and tokens, not per bot in dollars.
Today, instead: See turns, tokens and cost for every bot in Settings → Usage. Give a project a limit in minutes and tokens, and Murage stops starting new work at your limit. If you use Flux Router, set a spending cap on your Flux account. Loop detection flags a bot repeating the same call.
No SOC 2, HIPAA or outside security audit.
Today, instead: Read the code (AGPL-3.0) and hand your reviewer the security overview.
Video isn’t built in. A bot can call a video service you connect.
Everyone runs their own copy of Murage.
Today, instead: Build the team once, export it, and have each person import it on their own computer. Logins never travel with it.
Teach a skill and the built-in browser are on by default today.
Today, instead: Both are on by default. The built-in browser switch is in Settings → Devices, and Teach a skill is at the top of Settings → Skills.
Where the approval rules stop.
The approval rules are strong where they apply. Here’s where they don’t.
The stop line isn’t a sandbox.
It checks each action a bot tries to take. A bot on Auto or Full access runs with your user’s permissions, so keep a bot on Ask for anything where a mistake would be expensive. Read why, in the code
What it sees depends on the engine.
On Full access, the stop line judges the permission requests that reach Murage. On Claude Code and Codex, the stop line also covers tools from MCP servers you add. On Hermes and other ACP engines, Ask and the stop line cover only what the engine asks Murage about. When your own message names a recipient, a bot can record that as allowed for the task, and messages to that person then go ahead. What each engine covers
No limits turns it off.
On No limits the stop line doesn’t apply to your own chats (a routine still stops at it), though reading your keys still stops and asks. No limits is a desktop-only level you switch on yourself for one bot, after a warning.
Loop detection warns. You stop.
A bot repeating the same call gets flagged in the chat. It keeps going until you press Stop. The hand-off limits keep a team from passing work around forever, and none of them is a spending cap.
Computer use on Windows.
Not on your own Windows desktop in this release. On Windows, bots can use an isolated Local VM desktop or a cloud desktop on your own Box account.
How we check the rest, case by case: how we test Murage.
Try it on one job before you rely on it.
Give your first job to Murage.
Your team’s memory and files are stored on your computer, and the code is AGPL-3.0. If it isn’t for you, nothing is locked in.
No account needed · Runs on the AI plan you already pay for