Release notes, the support queue, renewal risk and the customer research nobody has time to synthesize. Brief your Chief of Staff and a team drafts each one for someone on your team to check.
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 answering tickets is an hour off the thing customers are waiting for.
Shipped, but nobody knows. The feature went out Thursday. The changelog, the email and the posts still 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-facing summary and a short email. Leave out internal work. Publish nothing.”
Still yours: the final wording and pressing Publish.
The jobs to hand off first. Each one ends with a draft or a question for you.
From Murage’s team library. Look inside any team before you import it, then export it once and share it with your staff.
Ship Software Safely
Get a scoped implementation plan, coordinated engineering work, and a release-readiness review backed by verification evidence.
SaaS MVP Sprint
Get an MVP specification, validation plan, landing-page copy, and visual direction.
Customer Success Org
Review account health, identify customers needing attention, and prepare renewal priorities and support follow-ups.
Support Stack
Prepare ticket triage, onboarding guidance, retention follow-ups, and reusable responses in your brand voice.
Growth Loop
Diagnose the biggest constraint using customer and performance evidence, then prioritize a growth experiment.
Find SEO Growth Opportunities
Assess demand and technical evidence, then get prioritized fixes, content briefs, and a practical SEO roadmap.
Why it fits this work
The release-notes brief asks for a merged pull request behind every line, and House Rules (your rules every bot reads first) tell bots never to report a result they didn’t get. Read the draft before you publish it.
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, you can switch any bot’s engine later, and the app is free.
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.
Murage is free and open source. Your bots run 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.
Memory, files and conversations are stored on your machine, not on our servers. The AI engine and any apps you connect receive what they need for the jobs you give them, under their own terms.
It works where you point it. A bot running Claude Code or Codex can change code in a folder you trust. Keep merges and deploys with your team; new bots start in Ask mode and ask before each action.
Through connected apps, with Flux Router credits or your own connected-apps key, where the app is in the catalog. MCP servers work too. Exports and pasted data always work.
Yes, each person on their own computer. Build the team once, export it, and every engineer, PM or support lead imports the same bots, skills and routines. Logins never travel with it. Each person can message their Chief from 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.
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
