Keep OpenClaw. Add the team around it.

Bring your OpenClaw agent into Murage, reachable alongside your other bots. It keeps OpenClaw’s own tools, and your Chief of Staff builds the team around it on Claude Code and Codex.

Murage runs this engine as a bot on your team. It’s a separate product, not a partnership.

The short answer

Same idea (your own open-source AI), but a Chief of Staff builds the team, and new bots ask before they act.

Which should you choose?

Murage runs the team

Murage

Open source
On your computer
The AI you choose

Who does the work: A Chief of Staff and a team

OpenClaw runs this bot

OpenClaw

Open source
Desktop and phone apps
Reachable from 29 chat apps

Who does the work: Multi-agent routing you configure

Download Murage

Checked October 2026 (October 9, 2026) against openclaw.ai, OpenClaw’s docs and its GitHub repository. The OpenClaw engine in Murage is not out yet.

Murage sits above OpenClaw.

You talk to one Chief of Staff. It builds the team, and each bot runs the engine that suits its job, on the plan or key you already have. An engine is the AI that does a bot’s thinking. To run teams and use tools, pick a tool-capable one: the built-in Fuigo engine with a supported model, Claude Code, Codex or Hermes. A plain OpenAI-compatible endpoint works for chat and drafting only. Portraits made with Murage’s own avatar generator. See every engine

OpenClaw runs inside Murage, as a bot’s engine

Keep OpenClaw. Add the team around it.

Pick OpenClaw as a bot’s engine (the AI that does its thinking) and your OpenClaw agent is reachable in Murage, alongside your other bots. If you run several OpenClaw agents, each one joins as its own bot. Your Chief of Staff can give it work; it answers alone, on OpenClaw’s own tools. On Ask, Murage runs an OpenClaw bot read-only, with no shell commands and no file changes. On Auto and Full access, OpenClaw’s own approval settings decide which actions ask you first. For work that needs Murage’s teammates, memory, connected apps or stop line, use a bot on Claude Code or Codex.

What Murage adds on top

A Chief of Staff that builds and runs a team for each job, with no routing to configure
Fuigo, Claude Code, Codex and Hermes as full engines with their tools, on your own plans
Each engine you pick installs from its card in Settings, and your Chief of Staff walks you through the rest

Why Murage is open source Every engine Murage runs

Here’s what came back this morning.

The brief

“Go through my inbox before I get in. Draft replies in my voice. Send nothing.”

What came back

Twelve emails came in. The team drafted eight replies, set four aside, and left two questions only the owner could answer. Nothing was sent.

Needs from you, in the team’s own report

Dana Brooks, Acme Studio · RenewalThe prior contract terms
Jordan Lee, Brightline Design · Pricing for 20 seatsThe per-seat price, and whether we offer a pilot
Priya S. · Export to PDF?Confirm the exact steps
Ben C. · Refund requestMoney. Check the billing record first

Replay of a real run on demo data. The company is made up. Engine: Flux Auto, worked 1m 41s. Watch the run

You know how this usually goes.

The agent says done. You go check. The wrong 10% looks exactly like the right 90%. Murage doesn’t promise better answers than the engine underneath. It changes what reaches you: drafts you check instead of messages sent, a source next to each claim in a research page, and a reviewer bot on any team you want one on. New bots start on Ask.

Keep OpenClaw. Murage runs it as a bot’s engine, and gives each bot a name, a job and a memory that lives in Murage. Change a bot’s engine next month and its job, notes and routines stay put. OpenClaw’s own chat history stays where it is; Murage doesn’t import it.

Try one job.

Pick something you know well: the weekly report, a research brief, a set of follow-up drafts. Brief the Chief once and check what comes back against what you asked for. If it isn’t for you, the team’s memory and files are stored on your computer in files you can open, and the code is AGPL-3.0.

See one job from brief to result What carries over when you switch Read the code on GitHub

At a glance.

Ten things buyers weigh up, including the ones where they’re ahead.

What matters

Murage

OpenClaw

The app needs no extra subscription
It runs on the AI plan or key you already have
Yes
Open source desktop app; Murage Cloud is optional and paid
Source
Yes
$0, MIT-licensed
Source
You choose which AI company does the work
Per bot or per task, from different vendors
Yes
Per bot: Fuigo, Claude Code, Codex, Hermes, a local model and more
Yes
Dozens of model providers, plus a Claude CLI backend and Codex through its app-server
Source
Named agents that keep their memory
A standing team that lasts beyond one task
Yes
Named bots, each with its own memory, kept on your computer
Partly
Multi-agent routing you configure
Source
Asks before acting outside, by default
Messaging someone new, posting, paying, deleting
Yes
New bots start on Ask; on Full access the stop line judges what each engine asks
Source
No
Host commands default to full access with asking off
Source
Memory stored on your computer
Not in a vendor’s cloud
Yes
Memory, files and chats on your computer
Yes
Markdown files on your disk
Source
Open source
A license you can read
Yes
AGPL-3.0
Source
Yes
MIT
Source
Reach it from your phone
Briefs and approvals away from the desk
Yes
An iPhone and Android app, plus your Chief in Telegram, Slack, Discord or WhatsApp
Yes
Native phone apps and 29 chat apps
Source
Keeps working with your computer off, today
Hosted or on a server
Yes
On any computer you leave on, including your own remote server. Murage Cloud (coming soon) will run one for you
Partly
If you run it on a server
Source
Native phone app
An iOS or Android app, not a web app or chat bot
Yes
iPhone and Android
Yes
Native iOS and Android apps
Source
SOC 2 report
What a procurement team will ask for
No
No SOC 2 report
Not stated
Not claimed: “no enterprise edition and no paid version”
Source

Each of OpenClaw’s marks links the page it comes from, checked October 9, 2026. “Not stated” means we couldn’t find it on the page named, not that it’s missing.

Both apps are open source. AI usage and any hosting or optional services are separate. OpenClaw is MIT-licensed; Murage is AGPL-3.0.

See one job from brief to result

Where your work lives.

Murage

Your computer

MemoryFilesChats

Your memory, files and chats are stored on your computer. What a bot sends to your AI, and to any app or service you connect, goes to them.

OpenClaw

A machine you host

MemoryConfig

It runs on your machine or a server you set up, with desktop apps and native phone apps to reach it.

Who does the work.

You brief one Chief of Staff. It builds a team of specialists for the job, and the team keeps its memory for next time. You can put a reviewer on any team to check work before it reaches you. Portraits made with Murage’s own avatar generator.

OpenClaw

One assistant you configure and reach everywhere; you set up routing across agents yourself.

What Murage adds for an OpenClaw user.

A team built for each job

Murage’s Chief of Staff builds a team of specialists for each job and runs it. With OpenClaw you configure multi-agent routing yourself.

Asks first by default

New bots start on Ask. On Full access, a bot stops before messaging anyone new, posting publicly, paying, or deleting outside its folder, unless you have allowed it for that task. On Hermes and other ACP engines, Ask and the stop line cover only what the engine asks Murage about. OpenClaw’s host commands run with full access unless you change them.

Claude Code and Codex as full engines

Each bot can run Fuigo or the real Claude Code, Codex or Hermes, with their tools, on your own plans. OpenClaw can run Claude through its Claude CLI backend and Codex through Codex’s app-server; Murage runs them as full engines under each bot, with the stop line on top.

Apps and teams out of the box

1,600+ connected apps through Flux Router or your own connected-apps key, and 79 ready-made team packages.

Where OpenClaw is ahead.

Fair’s fair. If one of these matters most to you, it may be the better choice today.

1
Far more chat apps
29 channels, including WhatsApp, iMessage and Signal. Murage reaches you on Telegram, Slack, Discord and WhatsApp.
2
Real phone calls
A voice-call plugin places phone calls with realtime voice. Murage’s calls happen in the app.
3
More model providers
Dozens of providers. Both run local models; OpenClaw supports more runtimes (vLLM, SGLang).
4
Native phone apps and a huge community
Native iOS and Android apps, about 391,500 GitHub stars (checked October 9, 2026), a nonprofit foundation and the ClawHub plugin marketplace. Murage has iPhone and Android apps too.

Which should you choose?

Same idea (your own open-source AI), but a Chief of Staff builds the team, and new bots ask before they act.

Choose Murage if

You want a Chief of Staff to build and run the team, and new bots to ask first (OpenClaw’s host commands default to full access with asking off)
You want Fuigo, Claude Code, Codex and Hermes running as full engines with their tools (OpenClaw runs Claude through its Claude CLI backend and Codex through Codex’s app-server; in Murage they sit under each bot with the stop line on top)
You’d rather have the team built for you than configure routing
You want ready-made teams for business jobs
You want to change a bot’s engine later without losing its job, notes, skills and routines

Download Murage

Choose OpenClaw if

You live in iMessage or Signal (29 chat apps; Murage reaches you on Telegram, Slack, Discord and WhatsApp)
You want it to place real phone calls, or to run on a server you host around the clock, today
You want a nonprofit-run project

Still deciding? Read how we check that a job is finished, then try one of your own.

Every detail.

Getting in

Price to start
MurageOpen source desktop app; Murage Cloud is an optional paid hosted service
OpenClaw$0 (MIT). “No subscription. No hosted tier. No token.”
Install
MurageDownload the app. Each engine you pick installs from its card in Settings, and your Chief of Staff walks you through the rest
OpenClawAn install script, npm (Node 24.16 or newer) or a desktop app, then `openclaw onboard --install-daemon` and configuration
Who runs the project
MurageFerrox Labs, with the code open under AGPL-3.0
OpenClawThe OpenClaw Foundation, an independent US nonprofit that signs every release

Where it runs

Runs on
MurageOn your computer
OpenClawYour machine or a server, as a gateway with desktop and phone apps
Keeps working with your laptop closed
MurageYes, on any computer you leave on, including your own remote server. Murage Cloud (coming soon) will look after one for you
OpenClawYes, if the gateway runs on a server you host; it has built-in cron jobs
Platforms
MurageMac, Windows and Linux, plus an iPhone app and an Android app; Telegram on your phone
OpenClawNative apps for macOS, iOS, Android, Windows and Linux
OpenClaw inside Murage
MuragePick OpenClaw as a bot’s engine and your OpenClaw agent is reachable in Murage beside your other bots. Your Chief of Staff can give it work; it answers alone, on OpenClaw’s own tools.
OpenClawNot applicable: it is its own app

Brains

Engines
MurageThe engine you choose, per bot: Fuigo (built in), Claude Code, Codex, Hermes, OpenClaw, Grok Build, Cursor, Google Antigravity, Kimi, Qwen, Droid, OpenCode, Pi, local models (Ollama, LM Studio) and any OpenAI-compatible API (chat only). Local models run through Ollama, LM Studio and llama.cpp
OpenClawHosted, subscription-backed, gateway or local models: dozens of providers (64 pages, some for speech, media and search), including Ollama, llama.cpp, LM Studio, vLLM and SGLang
Claude Code and Codex
MurageEach bot can run Fuigo or the real Claude Code, Codex or Hermes with their own tools, on your own plans
OpenClawCan run Claude through the Claude CLI backend and Codex through Codex’s app-server
Pick the model per helper
MurageChoose the engine and model for each bot, and change it later; memory, skills and approvals stay put
OpenClawModels and fallbacks are set in config; the Claude CLI backend can be a primary runtime or a fallback
Usage
MurageNothing from us. Your AI provider bills as usual. Flux Router, Ferrox Labs’ optional credit-billed service, covers AI models, connected apps, voice, images and web search if you use it; your own keys work instead
OpenClawYour model bill only

The team

Who leads
MurageEmber, your Chief of Staff, takes the brief and builds the team for each job, with no routing to configure
OpenClawYou set up multi-agent routing: isolated sessions per agent, workspace or sender
Helpers that last
MurageNamed bots with faces, voices and memory, still there tomorrow and on routines
OpenClawAgents with their own workspace and memory; skills load on demand
Projects with boards
MurageYes: a lead splits the goal into cards on a board and you sign off when it’s done
OpenClawNot described in the docs checked
Ready-made teams
Murage79 ready-made teams for business jobs
OpenClawCommunity skills and plugins through ClawHub

Hands

Apps
Murage1,600+ apps through Flux Router or your own connected-apps key, plus any public API and any MCP
OpenClawPlugins and skills from ClawHub, hooks and webhooks
Your own signed-in browser
MurageMurage for Chrome works in your own signed-in Chrome, in the tabs you share
OpenClawBrowses the web, fills forms, reads and writes files and runs shell commands, with full or sandboxed access
What an OpenClaw bot gets inside Murage
MurageAn OpenClaw bot runs on OpenClaw’s own tools. Murage’s teammates, memory, computer, browser and connected apps aren’t available on it. For work that needs Murage’s teammates, memory, connected apps or stop line, use a bot on Claude Code or Codex.
OpenClawIts own tools: browser, files, shell and plugins
Memory
MurageDesktop: on your computer, open to read and edit. Cloud: on your EU-hosted server, encrypted with a key Ferrox Labs holds
OpenClawPlain Markdown files in the agent’s workspace, searchable, with “no hidden state”

Control

Asks before acting
MurageNew bots start on Ask. On Full access, a bot stops before messaging anyone new, posting publicly, paying, or deleting outside its folder, unless you have allowed it for that task. Replies in an existing conversation go ahead on Auto and Full access. No limits turns the stop line off for your own chats; routines still stop at it.
OpenClawExec approvals are opt-in: host commands default to full access with asking off. Unknown senders get a pairing step by default
On an OpenClaw bot inside Murage
MurageOn Ask, Murage runs an OpenClaw bot read-only, with no shell commands and no file changes. On Auto and Full access, OpenClaw’s own approval settings decide which actions ask you first. Set approvals in OpenClaw, and put sends and payments on a Claude Code or Codex bot if you want Murage to stop and ask
OpenClawYou set strictness yourself: deny, allowlist or full, with ask off, on-miss or every command
Lessons you can see, edit and undo
MurageYes: correct a bot once and the lesson shows up where you can edit or undo it
OpenClawMemory files you edit by hand; skills it can write for itself
Open source
MurageYes, AGPL-3.0
OpenClawYes, MIT

Your data

Where memory lives
MurageDesktop: on your computer, open to read and edit. Cloud: on your EU-hosted server, encrypted with a key Ferrox Labs holds
OpenClawOn your disk, in the agent’s workspace
What leaves your machine
MurageYour memory and files stay on your computer; your AI provider sees what the engine sends it
OpenClawA daily version check by default, which you can switch off; anonymous feature statistics are opt-in

Reach

Chat apps
MurageMessage your Chief of Staff on Telegram, Slack, Discord or WhatsApp
OpenClaw29 channels, including WhatsApp, Telegram, Slack, Discord, iMessage, Signal and Teams
Voice
MurageCall any bot in the app and just talk; bots leave voice notes. Ask your Chief for a voice note in Telegram, Slack, Discord or WhatsApp, and on WhatsApp send it one of your own
OpenClawReal phone calls through a voice-call plugin (Twilio, Telnyx or Plivo), with realtime voice
Phone
MurageiPhone and Android app that opens your workspace: approvals, questions and calls with your team
OpenClawNative iOS and Android apps
For your staff
MurageEach person runs Murage on their own computer; export a team and everyone imports it, with no Murage seat fees
OpenClawThe gateway can run as a shared team deployment

Question	Murage	OpenClaw
Getting in
Price to start	Open source desktop app; Murage Cloud is an optional paid hosted service	$0 (MIT). “No subscription. No hosted tier. No token.”
Install	Download the app. Each engine you pick installs from its card in Settings, and your Chief of Staff walks you through the rest	An install script, npm (Node 24.16 or newer) or a desktop app, then `openclaw onboard --install-daemon` and configuration
Who runs the project	Ferrox Labs, with the code open under AGPL-3.0	The OpenClaw Foundation, an independent US nonprofit that signs every release
Where it runs
Runs on	On your computer	Your machine or a server, as a gateway with desktop and phone apps
Keeps working with your laptop closed	Yes, on any computer you leave on, including your own remote server. Murage Cloud (coming soon) will look after one for you	Yes, if the gateway runs on a server you host; it has built-in cron jobs
Platforms	Mac, Windows and Linux, plus an iPhone app and an Android app; Telegram on your phone	Native apps for macOS, iOS, Android, Windows and Linux
OpenClaw inside Murage	Pick OpenClaw as a bot’s engine and your OpenClaw agent is reachable in Murage beside your other bots. Your Chief of Staff can give it work; it answers alone, on OpenClaw’s own tools.	Not applicable: it is its own app
Brains
Engines	The engine you choose, per bot: Fuigo (built in), Claude Code, Codex, Hermes, OpenClaw, Grok Build, Cursor, Google Antigravity, Kimi, Qwen, Droid, OpenCode, Pi, local models (Ollama, LM Studio) and any OpenAI-compatible API (chat only). Local models run through Ollama, LM Studio and llama.cpp	Hosted, subscription-backed, gateway or local models: dozens of providers (64 pages, some for speech, media and search), including Ollama, llama.cpp, LM Studio, vLLM and SGLang
Claude Code and Codex	Each bot can run Fuigo or the real Claude Code, Codex or Hermes with their own tools, on your own plans	Can run Claude through the Claude CLI backend and Codex through Codex’s app-server
Pick the model per helper	Choose the engine and model for each bot, and change it later; memory, skills and approvals stay put	Models and fallbacks are set in config; the Claude CLI backend can be a primary runtime or a fallback
Usage	Nothing from us. Your AI provider bills as usual. Flux Router, Ferrox Labs’ optional credit-billed service, covers AI models, connected apps, voice, images and web search if you use it; your own keys work instead	Your model bill only
The team
Who leads	Ember, your Chief of Staff, takes the brief and builds the team for each job, with no routing to configure	You set up multi-agent routing: isolated sessions per agent, workspace or sender
Helpers that last	Named bots with faces, voices and memory, still there tomorrow and on routines	Agents with their own workspace and memory; skills load on demand
Projects with boards	Yes: a lead splits the goal into cards on a board and you sign off when it’s done	Not described in the docs checked
Ready-made teams	79 ready-made teams for business jobs	Community skills and plugins through ClawHub
Hands
Apps	1,600+ apps through Flux Router or your own connected-apps key, plus any public API and any MCP	Plugins and skills from ClawHub, hooks and webhooks
Your own signed-in browser	Murage for Chrome works in your own signed-in Chrome, in the tabs you share	Browses the web, fills forms, reads and writes files and runs shell commands, with full or sandboxed access
What an OpenClaw bot gets inside Murage	An OpenClaw bot runs on OpenClaw’s own tools. Murage’s teammates, memory, computer, browser and connected apps aren’t available on it. For work that needs Murage’s teammates, memory, connected apps or stop line, use a bot on Claude Code or Codex.	Its own tools: browser, files, shell and plugins
Memory	Desktop: on your computer, open to read and edit. Cloud: on your EU-hosted server, encrypted with a key Ferrox Labs holds	Plain Markdown files in the agent’s workspace, searchable, with “no hidden state”
Control
Asks before acting	New bots start on Ask. On Full access, a bot stops before messaging anyone new, posting publicly, paying, or deleting outside its folder, unless you have allowed it for that task. Replies in an existing conversation go ahead on Auto and Full access. No limits turns the stop line off for your own chats; routines still stop at it.	Exec approvals are opt-in: host commands default to full access with asking off. Unknown senders get a pairing step by default
On an OpenClaw bot inside Murage	On Ask, Murage runs an OpenClaw bot read-only, with no shell commands and no file changes. On Auto and Full access, OpenClaw’s own approval settings decide which actions ask you first. Set approvals in OpenClaw, and put sends and payments on a Claude Code or Codex bot if you want Murage to stop and ask	You set strictness yourself: deny, allowlist or full, with ask off, on-miss or every command
Lessons you can see, edit and undo	Yes: correct a bot once and the lesson shows up where you can edit or undo it	Memory files you edit by hand; skills it can write for itself
Open source	Yes, AGPL-3.0	Yes, MIT
Your data
Where memory lives	Desktop: on your computer, open to read and edit. Cloud: on your EU-hosted server, encrypted with a key Ferrox Labs holds	On your disk, in the agent’s workspace
What leaves your machine	Your memory and files stay on your computer; your AI provider sees what the engine sends it	A daily version check by default, which you can switch off; anonymous feature statistics are opt-in
Reach
Chat apps	Message your Chief of Staff on Telegram, Slack, Discord or WhatsApp	29 channels, including WhatsApp, Telegram, Slack, Discord, iMessage, Signal and Teams
Voice	Call any bot in the app and just talk; bots leave voice notes. Ask your Chief for a voice note in Telegram, Slack, Discord or WhatsApp, and on WhatsApp send it one of your own	Real phone calls through a voice-call plugin (Twilio, Telnyx or Plivo), with realtime voice
Phone	iPhone and Android app that opens your workspace: approvals, questions and calls with your team	Native iOS and Android apps
For your staff	Each person runs Murage on their own computer; export a team and everyone imports it, with no Murage seat fees	The gateway can run as a shared team deployment

Same job, both ways.

Five real jobs, walked through with Murage and with OpenClaw.

1
Text your assistant from the chat app you live in
With Murage
Message Ember on Telegram, Slack, Discord or WhatsApp. Ember takes the brief and hands the work to the right bot; iMessage and Signal aren’t on the list.
With OpenClaw
Message your agent in any of 29 channels, including iMessage and Signal, and it replies in the same chat.
2
Research three competitors and write a brief
With Murage
Ember builds a small team: a researcher per competitor and a writer. They share a project board, and the brief lands as a file in your folder.
With OpenClaw
One OpenClaw agent researches and writes, or you set up multi-agent routing to split the work.
3
Keep a job running overnight
With Murage
Set a routine on a bot and it runs while your computer is on. Murage Cloud (coming soon) runs your team with your computer off.
With OpenClaw
Run the gateway on a server you host and use its cron jobs, so the job runs while your laptop is closed.
4
Build a feature with Claude Code and have Codex review it
With Murage
Put Claude Code on one bot and Codex on another under Ember, on one project board. Each runs with its own tools and the stop line asks first.
With OpenClaw
OpenClaw can use the Claude CLI backend and run Codex through its app-server, configured by you in the gateway.
5
Approve something while you’re away
With Murage
A bot on Claude Code or Codex pauses at the stop line, the iPhone or Android app shows the ask, and you answer yes or no.
With OpenClaw
Exec approvals are off by default. With them on, a prompt that can’t reach anyone is denied.

Already using OpenClaw: your first day with Murage

Keep OpenClaw running. Pick it as a bot’s engine and your OpenClaw agent joins Murage beside your other bots.

1
Install Murage on your Mac, Windows or Linux computer. Your OpenClaw setup, chats and memory stay where they are.
2
Pick Claude Code or Codex for your first bot: its card installs it in one press and you sign in on the engine’s own screen.
3
Meet Ember, your Chief of Staff, and describe a job you now configure routing for in OpenClaw.
4
Add your OpenClaw agent as a bot. It keeps OpenClaw’s own tools.
5
Let the first run ask before it sends anything, then correct what you want changed and watch the lesson appear.

Questions about Murage and OpenClaw.

Does an OpenClaw bot get Murage’s tools?

No. An OpenClaw bot runs on OpenClaw’s own tools. Murage’s teammates, memory, computer, browser and connected apps aren’t available on it. For work that needs Murage’s teammates, memory, connected apps or stop line, use a bot on Claude Code or Codex.

Does Murage’s stop line cover an OpenClaw bot?

Not the way it covers Claude Code and Codex. On Ask, Murage runs an OpenClaw bot read-only, with no shell commands and no file changes. On Auto and Full access, OpenClaw’s own approval settings decide which actions ask you first. Murage’s stop line covers what an engine asks Murage about, so set OpenClaw’s approvals in OpenClaw, and put sends and payments on a Claude Code or Codex bot if you want Murage to stop and ask.

Can Murage run OpenClaw as an engine?

Yes. Pick OpenClaw as a bot’s engine and your OpenClaw agent is reachable in Murage alongside your other bots, on OpenClaw’s own tools. Your Chief of Staff can give it work; it answers alone, on OpenClaw’s own tools. If you run several OpenClaw agents, each one joins as its own bot. Today that is the OpenClaw on your own computer; connecting to an OpenClaw on another machine is planned.

Is Murage open source like OpenClaw?

Yes. Both apps are open source; you pay your AI provider. Connected apps and voice in Murage use Flux Router credits or your own keys (a connected-apps key for apps; OpenAI, xAI, Groq, OpenRouter or ElevenLabs for voice).

Can OpenClaw run Claude Code and Codex too?

Yes, in its own way: it can run Claude through its Claude CLI backend, which streams and reaches tools over an MCP bridge, and run Codex through Codex’s app-server. Murage runs them as full engines under each bot, with its stop line on top.

Can I run Murage on a server?

Yes. Murage Cloud (coming soon) runs your own Murage on a private server we look after. The desktop app runs on your computer.

Switching from OpenClaw or Hermes?

What carries over, what doesn’t and a first week: Switching to Murage.

Can my staff use it too?

Yes. Each person runs Murage on their own computer, with their own AI sign-in. Build a team once, export it, and everyone imports the same bots, skills and routines; logins never travel. Bots can post drafts to your team’s Slack channels through connected apps, with your approval. Shared workspaces for teams are coming soon to Murage Cloud.

Sources, checked October 9, 2026

Murage is made by Ferrox Labs, a small team. Spotted something out of date? Tell us and we’ll fix it.

OpenClaw is a trademark of its owner. Murage is not affiliated with or endorsed by the OpenClaw Foundation; the names and logos are used only to identify the products compared.

Get started in four steps

1
Download Murage
For Mac, Windows and Linux.
2
Pick an engine
Fuigo, Claude Code, Codex or Hermes on the plan you already pay for, a local model or an API key.
3
Meet Ember
Your Chief of Staff, who builds the team for each job.
4
Give it the first job
Start small. New bots ask before they act.

Download Murage All downloads and install notes

Give your first job to Murage.

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.

Download Murage

No account needed · Runs on the AI plan you already pay for

Keep OpenClaw. Add the team around it.

Bring your OpenClaw agent into Murage, reachable alongside your other bots. It keeps OpenClaw’s own tools, and your Chief of Staff builds the team around it on Claude Code and Codex.

Murage runs this engine as a bot on your team. It’s a separate product, not a partnership.

The short answer

Same idea (your own open-source AI), but a Chief of Staff builds the team, and new bots ask before they act.

Which should you choose?

Murage runs the team

Murage

Open source
On your computer
The AI you choose

Who does the work: A Chief of Staff and a team

OpenClaw runs this bot

OpenClaw

Open source
Desktop and phone apps
Reachable from 29 chat apps

Who does the work: Multi-agent routing you configure

Download Murage

Checked October 2026 (October 9, 2026) against openclaw.ai, OpenClaw’s docs and its GitHub repository. The OpenClaw engine in Murage is not out yet.

Question	Murage	OpenClaw
Getting in
Price to start	Open source desktop app; Murage Cloud is an optional paid hosted service	$0 (MIT). “No subscription. No hosted tier. No token.”
Install	Download the app. Each engine you pick installs from its card in Settings, and your Chief of Staff walks you through the rest	An install script, npm (Node 24.16 or newer) or a desktop app, then `openclaw onboard --install-daemon` and configuration
Who runs the project	Ferrox Labs, with the code open under AGPL-3.0	The OpenClaw Foundation, an independent US nonprofit that signs every release
Where it runs
Runs on	On your computer	Your machine or a server, as a gateway with desktop and phone apps
Keeps working with your laptop closed	Yes, on any computer you leave on, including your own remote server. Murage Cloud (coming soon) will look after one for you	Yes, if the gateway runs on a server you host; it has built-in cron jobs
Platforms	Mac, Windows and Linux, plus an iPhone app and an Android app; Telegram on your phone	Native apps for macOS, iOS, Android, Windows and Linux
OpenClaw inside Murage	Pick OpenClaw as a bot’s engine and your OpenClaw agent is reachable in Murage beside your other bots. Your Chief of Staff can give it work; it answers alone, on OpenClaw’s own tools.	Not applicable: it is its own app
Brains
Engines	The engine you choose, per bot: Fuigo (built in), Claude Code, Codex, Hermes, OpenClaw, Grok Build, Cursor, Google Antigravity, Kimi, Qwen, Droid, OpenCode, Pi, local models (Ollama, LM Studio) and any OpenAI-compatible API (chat only). Local models run through Ollama, LM Studio and llama.cpp	Hosted, subscription-backed, gateway or local models: dozens of providers (64 pages, some for speech, media and search), including Ollama, llama.cpp, LM Studio, vLLM and SGLang
Claude Code and Codex	Each bot can run Fuigo or the real Claude Code, Codex or Hermes with their own tools, on your own plans	Can run Claude through the Claude CLI backend and Codex through Codex’s app-server
Pick the model per helper	Choose the engine and model for each bot, and change it later; memory, skills and approvals stay put	Models and fallbacks are set in config; the Claude CLI backend can be a primary runtime or a fallback
Usage	Nothing from us. Your AI provider bills as usual. Flux Router, Ferrox Labs’ optional credit-billed service, covers AI models, connected apps, voice, images and web search if you use it; your own keys work instead	Your model bill only
The team
Who leads	Ember, your Chief of Staff, takes the brief and builds the team for each job, with no routing to configure	You set up multi-agent routing: isolated sessions per agent, workspace or sender
Helpers that last	Named bots with faces, voices and memory, still there tomorrow and on routines	Agents with their own workspace and memory; skills load on demand
Projects with boards	Yes: a lead splits the goal into cards on a board and you sign off when it’s done	Not described in the docs checked
Ready-made teams	79 ready-made teams for business jobs	Community skills and plugins through ClawHub
Hands
Apps	1,600+ apps through Flux Router or your own connected-apps key, plus any public API and any MCP	Plugins and skills from ClawHub, hooks and webhooks
Your own signed-in browser	Murage for Chrome works in your own signed-in Chrome, in the tabs you share	Browses the web, fills forms, reads and writes files and runs shell commands, with full or sandboxed access
What an OpenClaw bot gets inside Murage	An OpenClaw bot runs on OpenClaw’s own tools. Murage’s teammates, memory, computer, browser and connected apps aren’t available on it. For work that needs Murage’s teammates, memory, connected apps or stop line, use a bot on Claude Code or Codex.	Its own tools: browser, files, shell and plugins
Memory	Desktop: on your computer, open to read and edit. Cloud: on your EU-hosted server, encrypted with a key Ferrox Labs holds	Plain Markdown files in the agent’s workspace, searchable, with “no hidden state”
Control
Asks before acting	New bots start on Ask. On Full access, a bot stops before messaging anyone new, posting publicly, paying, or deleting outside its folder, unless you have allowed it for that task. Replies in an existing conversation go ahead on Auto and Full access. No limits turns the stop line off for your own chats; routines still stop at it.	Exec approvals are opt-in: host commands default to full access with asking off. Unknown senders get a pairing step by default
On an OpenClaw bot inside Murage	On Ask, Murage runs an OpenClaw bot read-only, with no shell commands and no file changes. On Auto and Full access, OpenClaw’s own approval settings decide which actions ask you first. Set approvals in OpenClaw, and put sends and payments on a Claude Code or Codex bot if you want Murage to stop and ask	You set strictness yourself: deny, allowlist or full, with ask off, on-miss or every command
Lessons you can see, edit and undo	Yes: correct a bot once and the lesson shows up where you can edit or undo it	Memory files you edit by hand; skills it can write for itself
Open source	Yes, AGPL-3.0	Yes, MIT
Your data
Where memory lives	Desktop: on your computer, open to read and edit. Cloud: on your EU-hosted server, encrypted with a key Ferrox Labs holds	On your disk, in the agent’s workspace
What leaves your machine	Your memory and files stay on your computer; your AI provider sees what the engine sends it	A daily version check by default, which you can switch off; anonymous feature statistics are opt-in
Reach
Chat apps	Message your Chief of Staff on Telegram, Slack, Discord or WhatsApp	29 channels, including WhatsApp, Telegram, Slack, Discord, iMessage, Signal and Teams
Voice	Call any bot in the app and just talk; bots leave voice notes. Ask your Chief for a voice note in Telegram, Slack, Discord or WhatsApp, and on WhatsApp send it one of your own	Real phone calls through a voice-call plugin (Twilio, Telnyx or Plivo), with realtime voice
Phone	iPhone and Android app that opens your workspace: approvals, questions and calls with your team	Native iOS and Android apps
For your staff	Each person runs Murage on their own computer; export a team and everyone imports it, with no Murage seat fees	The gateway can run as a shared team deployment

Murage

OpenClaw

Getting in

Price to start

Open source desktop app; Murage Cloud is an optional paid hosted service

$0 (MIT). “No subscription. No hosted tier. No token.”

Install

Download the app. Each engine you pick installs from its card in Settings, and your Chief of Staff walks you through the rest

An install script, npm (Node 24.16 or newer) or a desktop app, then `openclaw onboard --install-daemon` and configuration

Who runs the project

Ferrox Labs, with the code open under AGPL-3.0

The OpenClaw Foundation, an independent US nonprofit that signs every release

Where it runs

Runs on

On your computer

Your machine or a server, as a gateway with desktop and phone apps

Keeps working with your laptop closed

Yes, on any computer you leave on, including your own remote server. Murage Cloud (coming soon) will look after one for you

Yes, if the gateway runs on a server you host; it has built-in cron jobs

Platforms

Mac, Windows and Linux, plus an iPhone app and an Android app; Telegram on your phone

Native apps for macOS, iOS, Android, Windows and Linux

OpenClaw inside Murage

Pick OpenClaw as a bot’s engine and your OpenClaw agent is reachable in Murage beside your other bots. Your Chief of Staff can give it work; it answers alone, on OpenClaw’s own tools.

Not applicable: it is its own app

Brains

Engines

The engine you choose, per bot: Fuigo (built in), Claude Code, Codex, Hermes, OpenClaw, Grok Build, Cursor, Google Antigravity, Kimi, Qwen, Droid, OpenCode, Pi, local models (Ollama, LM Studio) and any OpenAI-compatible API (chat only). Local models run through Ollama, LM Studio and llama.cpp

Hosted, subscription-backed, gateway or local models: dozens of providers (64 pages, some for speech, media and search), including Ollama, llama.cpp, LM Studio, vLLM and SGLang

Claude Code and Codex

Each bot can run Fuigo or the real Claude Code, Codex or Hermes with their own tools, on your own plans

Can run Claude through the Claude CLI backend and Codex through Codex’s app-server

Pick the model per helper

Choose the engine and model for each bot, and change it later; memory, skills and approvals stay put

Models and fallbacks are set in config; the Claude CLI backend can be a primary runtime or a fallback

Usage

Nothing from us. Your AI provider bills as usual. Flux Router, Ferrox Labs’ optional credit-billed service, covers AI models, connected apps, voice, images and web search if you use it; your own keys work instead

Your model bill only

The team

Who leads

Ember, your Chief of Staff, takes the brief and builds the team for each job, with no routing to configure

You set up multi-agent routing: isolated sessions per agent, workspace or sender

Helpers that last

Named bots with faces, voices and memory, still there tomorrow and on routines

Agents with their own workspace and memory; skills load on demand

Projects with boards

Yes: a lead splits the goal into cards on a board and you sign off when it’s done

Not described in the docs checked

Ready-made teams

79 ready-made teams for business jobs

Community skills and plugins through ClawHub

Hands

Apps

1,600+ apps through Flux Router or your own connected-apps key, plus any public API and any MCP

Plugins and skills from ClawHub, hooks and webhooks

Your own signed-in browser

Murage for Chrome works in your own signed-in Chrome, in the tabs you share

Browses the web, fills forms, reads and writes files and runs shell commands, with full or sandboxed access

What an OpenClaw bot gets inside Murage

An OpenClaw bot runs on OpenClaw’s own tools. Murage’s teammates, memory, computer, browser and connected apps aren’t available on it. For work that needs Murage’s teammates, memory, connected apps or stop line, use a bot on Claude Code or Codex.

Its own tools: browser, files, shell and plugins

Memory

Desktop: on your computer, open to read and edit. Cloud: on your EU-hosted server, encrypted with a key Ferrox Labs holds

Plain Markdown files in the agent’s workspace, searchable, with “no hidden state”

Control

Asks before acting

New bots start on Ask. On Full access, a bot stops before messaging anyone new, posting publicly, paying, or deleting outside its folder, unless you have allowed it for that task. Replies in an existing conversation go ahead on Auto and Full access. No limits turns the stop line off for your own chats; routines still stop at it.

Exec approvals are opt-in: host commands default to full access with asking off. Unknown senders get a pairing step by default

On an OpenClaw bot inside Murage

On Ask, Murage runs an OpenClaw bot read-only, with no shell commands and no file changes. On Auto and Full access, OpenClaw’s own approval settings decide which actions ask you first. Set approvals in OpenClaw, and put sends and payments on a Claude Code or Codex bot if you want Murage to stop and ask

You set strictness yourself: deny, allowlist or full, with ask off, on-miss or every command

Lessons you can see, edit and undo

Yes: correct a bot once and the lesson shows up where you can edit or undo it

Memory files you edit by hand; skills it can write for itself

Open source

Yes, AGPL-3.0

Yes, MIT

Your data

Where memory lives

Desktop: on your computer, open to read and edit. Cloud: on your EU-hosted server, encrypted with a key Ferrox Labs holds

On your disk, in the agent’s workspace

What leaves your machine

Your memory and files stay on your computer; your AI provider sees what the engine sends it

A daily version check by default, which you can switch off; anonymous feature statistics are opt-in

Reach

Chat apps

Message your Chief of Staff on Telegram, Slack, Discord or WhatsApp

29 channels, including WhatsApp, Telegram, Slack, Discord, iMessage, Signal and Teams

Voice

Call any bot in the app and just talk; bots leave voice notes. Ask your Chief for a voice note in Telegram, Slack, Discord or WhatsApp, and on WhatsApp send it one of your own

Real phone calls through a voice-call plugin (Twilio, Telnyx or Plivo), with realtime voice

Phone

iPhone and Android app that opens your workspace: approvals, questions and calls with your team

Native iOS and Android apps

For your staff

Each person runs Murage on their own computer; export a team and everyone imports it, with no Murage seat fees

The gateway can run as a shared team deployment

Keep OpenClaw. Add the team around it.

Murage sits above OpenClaw.

Keep OpenClaw. Add the team around it.

Here’s what came back this morning.

You know how this usually goes.

Try one job.

At a glance.

Where your work lives.

Who does the work.

What Murage adds for an OpenClaw user.

A team built for each job

Asks first by default

Claude Code and Codex as full engines

Apps and teams out of the box

Where OpenClaw is ahead.

Which should you choose?

Choose Murage if

Choose OpenClaw if

Every detail.

Getting in

Where it runs

Brains

The team

Hands

Control

Your data

Reach

Same job, both ways.

Text your assistant from the chat app you live in

Research three competitors and write a brief

Keep a job running overnight

Build a feature with Claude Code and have Codex review it

Approve something while you’re away

Already using OpenClaw: your first day with Murage

Questions about Murage and OpenClaw.

Get started in four steps

Download Murage

Pick an engine

Meet Ember

Give it the first job

Read next.

Give your first job to Murage.

Search murage.ai

Keep OpenClaw. Add the team around it.

Murage sits above OpenClaw.

Keep OpenClaw. Add the team around it.

Here’s what came back this morning.

You know how this usually goes.

Try one job.

At a glance.

Where your work lives.

Who does the work.

What Murage adds for an OpenClaw user.

A team built for each job

Asks first by default

Claude Code and Codex as full engines

Apps and teams out of the box

Where OpenClaw is ahead.

Which should you choose?

Choose Murage if

Choose OpenClaw if

Every detail.

Getting in

Where it runs

Brains

The team

Hands

Control

Your data

Reach

Same job, both ways.

Text your assistant from the chat app you live in

Research three competitors and write a brief

Keep a job running overnight

Build a feature with Claude Code and have Codex review it

Approve something while you’re away

Already using OpenClaw: your first day with Murage

Questions about Murage and OpenClaw.

Get started in four steps

Download Murage