DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to share a configured bot team as one file with Open Maus Bot

Save a working team as one file a colleague can import without your chat history or keys.

Who it is forA person who has built a working bot setup and wants a teammate to start from the same bots, channels and instructions.

The problemRebuilding a working team by hand for a colleague wastes time and invites mistakes in instructions and channel setup.

The outcomeA team file that the colleague imports as new bots on Ask, with skills switched off and routines paused.

What you need first

  • A computer running macOS, Windows, or Ubuntu 24.04 x64, with the OpenMausBot app downloaded from openmausbot.com or the latest release page
  • At least one of the claude, codex or grok CLIs installed and logged in on your own machine
  • A team playbook .md file, either from BotMRR or the open-source playbook repository
  • Accounts for any apps you want bots to use, such as Gmail or Slack, approved through OAuth

Steps

  1. Right-click the team and choose Share team…, or use Templates → Share.
  2. Untick any starter notes you do not want to include.
  3. Read the dialog, which shows exactly what the file holds, before you save it.
  4. Send the saved file to your colleague.
  5. Your colleague imports the file and reviews the new bots, which start on Ask with skills off and routines paused.

Prompt for your agent

Using the OpenMausBot repo at github.com/milind-soni/OpenMausBot, export the team named <team-name> with Share team and list every item the dialog says the file contains. Expected output: that list and the file path. Verify that the list contains no chat history, keys, passwords or model choices.

Caveat. The README says chat history, keys, passwords, model choices and computers never go in the file, but you should still check the dialog before saving.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page