For businesses with 5 to 50 people. Build the bots, skills and routines once, export them, and everyone imports the same setup on their own computer. Drafts land in your Slack channels, each client gets its own project, and every new bot starts on Ask, so a person says yes before it acts until you give it 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
Everyone does it differently. Five people, five ways of writing the weekly update, and the good way lives in one person’s head.
The busywork scales with headcount. Every new hire brings more status updates, more meeting notes and more follow-ups nobody owns.
AI, one tab at a time. Everyone pastes into their own chatbot. Nothing is shared, nothing is repeatable, and nobody checks what went out.
Hand this off first: team digest to slack
“Every Friday at 3, draft the team update for #general: what shipped, what’s stuck, who needs help, and next week’s priorities. Show me before you post.”
Still yours: reading the digest and saying yes before it posts.
Paste the week’s notes, or connect the apps they live in. The team drafts Friday’s update and lists where each line came from. You check it, then say yes before it posts to Slack.
| Update line | Where it came from | Check before it goes |
|---|---|---|
| Shipped: the new booking form is live for all customers. | Thursday’s release note | Did the rollout finish for every customer? |
| Open: two support tickets about invoice emails, both waiting on a reply. | Support inbox, Friday morning | Who owns the two replies? |
| Next week: one person is out Monday and Tuesday. | Team calendar | Is cover arranged for their clients? |
From Murage’s team library. Look inside any team before you import it, then export it once and share it with your staff.
Business / Team
Get a scoped brief, a working draft, and a review that separates evidence from assumptions and open decisions.
Back-Office Crew
Turn operational issues into a prioritized daily action list with financial context and clear follow-ups.
Reply Desk
Sort the queue, prepare replies in your voice, and flag promising sales conversations for follow-up.
Sales Org
Review the pipeline, investigate stalled deals, and prepare outbound priorities using buyer research and offer analysis.
Customer Success Org
Review account health, identify customers needing attention, and prepare renewal priorities and support follow-ups.
War Room
Examine operational, financial, growth, risk, and customer perspectives, then get a go, no-go, or conditional recommendation.
Build one team package and share it with your staff. Each person imports it on their own computer and connects their own accounts. When you change the team, share the new version and they import it.
Sales
Ask modeSame team · own logins
Support
Ask modeSame team · own logins
Finance
Ask modeSame team · own logins
Operations
Ask modeSame team · own logins
Why it fits this work
Export a team and your staff import the same bots, skills and routines on their own computers. Logins never travel, so each person connects their own accounts.
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.
Bots post drafts to your Slack channels through connected apps, with your approval. Up to five labeled accounts per app, so work and client inboxes stay apart.
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.
Yes, each person on their own computer. Build the team once, export it, and every person on your team 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.
Yes. Give each client or department its own project with its own files, goal and team, so the work stays organized. Choose which bots, memories and connected accounts each project uses.
New bots start on Ask, so every action a bot tells Murage about waits for a yes. 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: shell commands and file edits. Replies in an existing conversation go ahead on Auto and Full access.
The app is free for every person. Each person uses an AI plan. Flux Router credits are optional, for anyone who chooses Flux for models, apps, voice, images or search; their own keys work instead.
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
