Key takeaways
- A team of AI bots in one chat app: each bot has its own personality, its own model and its own computer.
- Use the agents you already have. Bots run on your own Claude, Codex or Grok command-line tools, with no new accounts.
- Stay in control: risky actions such as shell commands and file edits appear as cards you allow or deny.
- Local first: transcripts and keys live in a folder on your machine, not in a cloud.
- The catches: the project calls itself early, Ubuntu is beta, and cloud computers use a paid third-party service.
What it is
OpenMausBot describes itself as the open-source Grok Bot alternative: your own team of AI bots, in a chat app. It is free, released under the Apache-2.0 licence, and the code is on GitHub at milind-soni/OpenMausBot.
The problem it solves
Closed personal-agent products keep the model, the computer and your data on their maker's side. OpenMausBot is an independent project that rebuilds the idea of a roster of bots you chat with, but on the agents you already have.
It uses your existing logins and subscriptions, with no new accounts and no proxy in the middle. It says it is not affiliated with xAI, Meta, OpenAI or Manus.
What you get
- Your own engines: bots run on the claude, codex and grok command-line tools already on your machine.
- A brain per bot: you can switch a bot's model mid-conversation.
- A computer per bot: each can use a cloud Linux desktop or an isolated local virtual machine.
- Decisions stay with you: a permission broker turns every risky action into a decision you make, shown as a card in the chat.
- Connected apps: connect an app once with OAuth and every bot can use it as a tool.
The catches
- Maturity: the README calls it early but real, and warns that hosted and mobile connectivity is still being built.
- Platforms: Ubuntu remains a beta, host control is disabled on Ubuntu Wayland, and the Windows installer is not code-signed yet.
- Cost: cloud computers use a third-party service that is paid after its trial.
- Privacy: usage analytics are anonymous and optional, with a setting to turn them off. Keys entered in terminal setup are saved as plaintext in a private config file.
- Licence: an enterprise folder is source-available under its own licence, and running from source needs Node 24 or newer.
What we did not test
We did not install OpenMausBot, run any bot, try the cloud computers or check the approval cards. Every claim here comes from a literal quote in the project's README or the GitHub API, and the feature descriptions are the project's own.
Verdict
Editors' view: this is for people who already pay for Claude or Codex and like the idea of managing several agents like contacts in a messaging app, with local data. If you want something finished and fully hosted, the project's own warning about rough edges applies. Try it with low-risk tasks first.
Sources
Need help adopting this, or have a software project in mind?
Tell us what you are building. The initial consultation is free. Email [email protected] or follow @zolnaltd.
Start a conversation →