Keep your builders on the roadmap. Murage gives you a Chief of Staff and a team that drafts release notes and support replies and flags renewal risk, each bot on the engine you pick. New bots start on Ask, so on Claude Code and Codex every message waits for your yes until you give a bot more room.
Free and open source. macOS, Windows and Ubuntu.
An example view. The teams are real, from the library. None of them is running yet.
Teams
Support eats the roadmap. Every hour an engineer spends on tickets is an hour off what customers are waiting for.
Shipped, but nobody knows. The feature went out Thursday. The changelog, the email and the posts haven’t.
Churn you saw too late. The signs were in the usage data and the tickets. Nobody had time to read them.
Hand this off first: release notes
“Every Thursday, read this week’s merged pull requests. Draft the changelog entry, a customer email and two posts. Plain English, no internal jargon.”
Each job starts with one sentence to your Chief of Staff, and ends with a draft or a question for you.
Drafts replies and a ranked fix list. Sending stays with you.
“Go through the support inbox every morning at 7. Draft answers from our docs, tag bugs, and give me the top three themes this week.”
From your CRM, billing and usage exports or connected apps.
“Every Monday at 8, review the accounts renewing in the next 90 days. Tell me which look at risk, why, and the move to make on each.”
Every theme comes with the quotes behind it.
“Here are 20 interview transcripts and last month’s support themes. Give me the five problems customers mention most, with quotes, and what to build first.”
You check the numbers and send it.
“Draft this month’s investor update in last month’s format. Here are the metrics and the three things that happened.”
Why it fits this work
Give the builder bot Claude Code and the reviewer Codex, or the other way around, so a second model reads the work before anyone on your team does.
Claude Code, Codex, Hermes and more, each bot on the engine that suits its job. Keep the one you use; Murage puts them on one team, and you can switch any bot’s engine later.
The Murage app is free. Your team runs on the AI plan you already pay for, and a busy team uses its allowance faster. Connected apps and voice use optional Flux Router credits or your own keys.
Your Chief of Staff hands each part of the job to a specialist, can run it on a schedule, and gives you the draft.
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. On Hermes and other ACP engines, Ask and the stop line cover only what the engine asks Murage about: shell commands and file edits.
From Murage’s library. Look inside any team before you import it.
It takes the recurring non-engineering work: release notes, support drafts, renewal risk, research synthesis and investor updates. Your team stays on the product.
Each bot can run on its own engine: Claude Code, Codex, Hermes, Grok Build, Cursor, Google Antigravity, Kimi, Qwen, Droid, OpenCode, Pi, Fuigo (built in), local models (Ollama, LM Studio) and any OpenAI-compatible API (chat only). OpenClaw is coming. Type / to use each engine’s own commands.
Coding engines work under the approval level you set, and deleting outside the bot’s folder stops for you, even on Full access. On Hermes and other ACP engines, Ask and the stop line cover only what the engine asks Murage about: shell commands and file edits. Keep merge and deploy with your team.
Yes, each person on their own computer. Build the team once, export it, and everyone on your team imports the same bots, skills and routines. Logins never travel with it. Each person’s Chief reaches them in Slack, Discord or Telegram, and bots can post drafts to your team’s Slack channels through connected apps, with your approval and up to five labeled accounts per app. Shared, always-on workspaces come with Murage Cloud, which isn’t open yet.
Murage is free and open source, and your agents run on the AI plan you already pay for. Connected apps like Gmail use Flux Router credits or your own connected-apps key.
We build your first team with you, connect your tools and write your House Rules. Tell us what you need and we’ll quote before anything is booked.
Start with one job this week: release notes.
Download the free 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
