MURAGE™
How it worksFeaturesSolutionsUse casesComparePricingLearn
DownloadDownload
MURAGE™

An AI Chief of Staff and a team that does the work. Open source, from Ferrox Labs.

Product

  • Features
  • How it works
  • Engines and apps
  • Privacy and security
  • Pricing
  • Murage Cloud
  • Download
  • Changelog
  • FAQ

Solutions

  • Solopreneurs
  • Founders and startups
  • Agencies
  • Ecommerce
  • Small business
  • Creators and educators
  • Developers
  • SaaS
  • Nonprofits
  • Consultants and freelancers
  • Customer success teams
  • Legal and professional services
  • Small teams
  • Sales teams
  • Operations managers
  • OpenClaw and Hermes
  • Industries
  • Use cases
  • Build your team

Compare

  • vs Claude Code
  • vs Codex (ChatGPT Work)
  • vs Claude (Cowork)
  • vs Paperclip
  • vs OpenClaw
  • vs Hermes Agent
  • vs Manus
  • vs Genspark
  • vs n8n
  • vs Zapier
  • vs Grok Bot
  • vs Meta Muse
  • vs Claude Duet
  • vs OpenAI Dots
  • vs Cue by Manus
  • vs Instinct
  • vs Viktor
  • vs Lindy
  • vs Tasklet

Resources

  • Learn
  • Docs
  • Team library
  • Team gallery
  • Skill library
  • AI Chief of Staff
  • How we test
  • Limits
  • Switching to Murage
  • Open source
  • Blog
  • Community on Discord
  • Release notes

Company

  • About
  • Why trust Murage
  • Press
  • Partners
  • Enterprise
  • Contact
  • Privacy
  • Terms
  • Cookies

© 2026 Ferrox Labs, LLC. Murage is open source under AGPL-3.0. Murage™ is a trademark of Ferrox Labs, LLC.

Getting started · Episode 12 of 17

Teams that talk to each other

4:31

Chapters

Add a second business as its own team, with its own memory. Then let a bot on one team ask a bot on another for help, choose who may talk to whom, and share one bot between two teams.

What you'll learn

  • Give a second line of business its own team and leader
  • Choose who a bot may talk to, one name at a time
  • Allow the hand-off the first time, and watch it in the chat
  • Share one bot with two teams instead of hiring twice
Read the transcript

Maya's Business Planner needed posts to sell workshop seats, so it asked Buzz, a bot on another team. Buzz drafted the week and sent it straight back. That's teams that talk to each other. Our founder runs four businesses on one Murage. One roster, one Inbox, one chief of staff. Today Maya adds a second business, workshops, as its own team. You'll see one bot ask a bot on another team for help, how you decide who may talk to whom, and one bot shared by two teams. Let's grow. Step one: a second line of business gets its own team. Plus, New Team. Pick from my bots. Workshops, for Maya's golden-hour portrait days next year. A different business from weddings. A team needs at least one bot, so Business Planner moves over to run workshops. Create. And there's Workshops, a new section in the sidebar, with one bot in it. Right-click it, Make Team leader. This team's memory starts here, separate from the weddings. Step two: who may it talk to? By default, its team, its lead, and Ember. Bot settings, Permissions. Can talk to. My team, Everyone, or pick. Maya picks: Business Planner may talk to Buzz, on Social Week. One-way, so Buzz only answers what it's asked. Trust, one name at a time. Replies go back to whoever asked. Nothing to set on Buzz's side. Step three: the hand-off. A new task with Business Planner. Maya briefs it: ask Buzz for a fresh seven-day plan with captions, drafts only, no images, then bring it back with your note. Send. It thinks, and then it stops: handing work to another bot is an action, and Maya's on Ask, so it checks with her first. A few minutes later: Allow once. Messaged Buzz. That chip is the hand-off, right there for you to see. And by the time Maya looks, Buzz has already answered, right under it. Over on Social Week, Buzz got a message from a bot, not from Maya. Message from Business Planner, it says. And Buzz did what Buzz does: a week of posts, as drafts, text only. Back with Business Planner: the whole week, word for word. Business Planner doesn't build on it until Maya's next word. So she gives it: your week's back, now your note. A minute later: Thursday, Saturday and Sunday, with reasons, saved to a file. Drafts only, nothing posted or scheduled. Two teams, one job, and Maya typed two lines. Step four: one bot, two teams. Draft Partner answers wedding enquiries; workshop ones read much the same, so why hire twice? Bot settings, Teams, Shared with. These teams: Workshops. Save. It keeps separate notes and a folder for each team, and takes one job per team at a time. Close it, and there in the sidebar: Draft Partner, shared from the studio, now under Workshops too. Step five: step back. Three teams, a project under one, and bots that cross over when Maya says so. Our founder runs four businesses on one Murage. And over all of it, one Ember and one Inbox, where every team's asks land. That's teams that talk to each other. A team per business, each with its own memory. Open a line between bots one name at a time, and watch the hand-off right in the thread; replies come back to whoever asked. Share one bot instead of hiring twice. Got a side business? Give it a team tonight. Whatever you run, each business gets its own team and its own memory. Your bots hand work across when you say so, and every ask lands in one Inbox. Download it free at murage.ai.

Previous, episode 11Projects: one room for every big jobNext, episode 13Work with your PDFs: six leases into one table
Download it at murage.ai