Your listings, promo calendar and “where’s my order” queue, drafted by a morning routine while your computer is on. Your team checks the drafts and sends them. Refunds and anything else that pays stop for your yes, even on Full access.
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
A listing for every product. Every product needs copy, and every platform wants it different.
The promo scramble. Sales, launches and restocks, planned the week before, every time.
Where is my order? The support queue never stops, and half of it is the same five questions.
Hand this off first: inbox triage
“Go through my inbox before I get in. Draft replies in my voice. Send nothing.”
Still yours: the facts the drafts are missing, and pressing Send. Refunds stop for your yes, even on Full access.
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.
Ecommerce Engine
Review product positioning and customer friction, then prepare listing, campaign, and support improvements.
Listing Forge
Research the buyer and write a platform-appropriate listing, with a quality check before publication.
Promo Calendar War-Room
Build a dated promotion calendar, deal copy, and a checklist for restoring normal offers afterward.
Winning Product War Room
Review demand evidence, likely economics, and quality concerns in a one-page go/no-go assessment.
Review Engine
Prepare response drafts and review-request messages, then turn recurring feedback into a prioritized improvement digest.
Email & Lifecycle Crew
Draft lifecycle email flows and a broadcast calendar grounded in audience needs and performance evidence.
Why it fits this work
Paying anyone, refunds included, stops and asks, even on Full access. The team drafts the customer reply; the refund decision waits for you.
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.
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.
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.
Memory, files and conversations are stored on your computer, not on our servers. The AI and apps you connect receive what each job needs.
Connected apps come through Flux Router or your own connected-apps key. Check the app’s connection list for your platform; you can always paste data in.
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.
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
