TL;DR
OpenMausBot (milind-soni/OpenMausBot), also sold as MausBot and formerly called OpenGrokBot, is a desktop chat app in which every contact is an AI agent. Each bot runs on a coding-agent CLI you already have installed and logged in (claude, codex or grok), has its own personality and model, can be given a computer (a cloud Linux desktop, a local VM, or with your explicit opt-in your own machine), and can use hundreds of apps through Composio. Risky actions show up in the chat as Allow / Deny cards.
Facts as of November 13, 2026:
- 21,954 GitHub stars and 3,044 forks. The repository was created on August 11, 2026, so that is three months of growth; it was on GitHub’s weekly trending list this week with about 9,100 new stars.
- 718 open issues (issues only; GitHub’s counter shows 1,033 because it adds 315 open pull requests) and 514 closed.
- Latest release: v0.1.154, published November 12, 2026. There have been 111 releases in three months, and the npm package
openmausbotis on the same version. - License: Apache-2.0, except the
enterprise/folder, which is source-available under its own license. Delete that folder and what remains is the open-source edition.
Not run by us: our hands-on lab (a throwaway GitHub Actions container) refused to start the job today because of an account billing problem, and beyond starting up, the app needs a logged-in Claude, Codex or Grok CLI or a provider API key to do anything. This review is based on the README, the docs folder, the release notes, the issue tracker and community threads.
Our verdict: OpenMausBot is the most complete open-source take on the “team of agents in a messaging app” shape that Grok Bot, Meta Muse, OpenAI dots and Cue by Manus made popular this autumn. Its strongest idea is that it adds no model account of its own: it drives the agent CLIs and subscriptions you already pay for, and keeps transcripts in ~/.openmausbot. Its weaknesses are the ones you would expect from a three-month-old project that ships almost daily: a large issue backlog, Linux still in beta, and a growing commercial layer (MausBot Cloud, an enterprise folder) beside the open core. Try it if you already pay for two of the three agent CLIs and want them working side by side with approvals. Don’t expect it to keep working while your laptop is shut.
Quick Reference
| Field | Value |
|---|---|
| What it is | Desktop chat app where each contact is a local Claude, Codex or Grok agent with its own computer and apps |
| Repository | milind-soni/OpenMausBot |
| Stars (Nov 13, 2026) | 21,954 |
| Latest release | v0.1.154 (November 12, 2026) |
| License | Apache-2.0, plus a source-available enterprise/ folder |
| Platforms | macOS (Apple silicon and Intel, signed), Windows x64 (installer not code-signed), Ubuntu 24.04 x64 (beta) |
| Language | TypeScript (React + Vite + Tailwind UI, Electron shell, Node harness server) |
| Runtime requirement | Node 24+ for the npm and source paths; at least one of the claude, codex or grok CLIs logged in |
| Optional paid services | Boat (cloud desktops, paid after trial), Composio (connected apps), ElevenLabs or Fish Audio (voice) |
| Headless use | openmausbot CLI with JSON output and exit codes; stdio MCP server |
What OpenMausBot actually is
The README states the pitch in one line: “One assistant in one box is the wrong shape for agents.” Instead of one chat window, you get a sidebar of bots that behave like contacts, which you can group into channels with their own transcript, instructions, working folder and roster.
Underneath, two processes do the work:
- The harness server listens on
127.0.0.1:8799. It owns every agent process and has one driver per provider. Claude runs over its stream-JSON mode, Codex over JSON-RPC, and Grok Build over ACP. The server normalizes each provider’s protocol into one event stream, logged per thread as NDJSON. A permission broker turns shell commands, file edits and questions from any agent into approval cards. - The app is a React UI in an Electron shell. According to the README it “holds no transports of its own”: it sends typed HTTP commands to the harness and folds one Server-Sent Events stream into state.
The design choice that matters is “bring your own agents”. OpenMausBot doesn’t call a model API on your behalf by default. It starts the same claude or codex binary you use in a terminal, so your existing login, plan and rate limits apply. You can switch a bot’s model mid-conversation, and run Claude for one bot and Codex for another in the same channel.
On top of that sit features that make it more than a multi-CLI front end:
- Computers per bot. A bot can get a cloud Linux desktop from Boat (the project’s sponsor), an isolated local VM, or control of your own machine through the bundled Cua Driver. Host control works on macOS and Windows. On Ubuntu it is an explicit opt-in beta on Xorg and disabled on Wayland.
- Connected apps. Gmail, Slack, GitHub, Notion, Linear and others come through a one-click marketplace over Composio Sessions. You connect each with OAuth once and every bot can use it.
- Triggers. Bots can create schedules (once, on weekdays, or every 5–1,440 minutes), webhook triggers (a local receiver on port 8800) and app-event triggers (“whenever I get an email from Acme, draft a reply”).
- Voice and team files. Bots can read replies aloud or take a call (ElevenLabs, Fish Audio, xAI, Mac voices or local Chatterbox), and a whole department of bots can be exported to one Markdown file, minus chat history, keys and computer access.
Getting started
The quickest path is a release build: a signed .dmg for macOS, a setup.exe for Windows, or a .deb / AppImage for Ubuntu 24.04. The harness is embedded, so there is no separate server to run. Install at least one agent CLI first and log in, and it shows up in the model picker.
Without the desktop app, the README offers an npm path (Node 24 or newer):
npm install -g openmausbot
openmausbot # first launch: choose AI access, sign in or paste a key, pick a model
From source, it is pnpm install, then pnpm dev:server (harness on port 8799), pnpm dev (app on port 5199) and pnpm dev:desktop (the Electron shell).
To run it on a VPS or a home server, openmausbot serve takes one way in and prints a single pairing link that you paste into the desktop app under + → Connect to a server:
npx openmausbot setup
npx openmausbot serve --tailscale # or --public-url, --domain, --lan, --tunnel
The self-hosting guide’s one hard rule: never forward port 8799 yourself, because a program on the server’s own machine counts as its owner.
The headless CLI is the underrated part
For developers, the most interesting piece is the openmausbot command, which drives a running workspace without a screen. The documented flow:
openmausbot serve --no-pair &
openmausbot engine set claude --key-env ANTHROPIC_API_KEY
openmausbot team apply launch-room.yaml
openmausbot run "Room Lead" "Rehearse the launch of https://example.com" --export ./rehearsal
run gives a bot or channel one job, waits until it and every teammate it delegated to are done, then prints the final reply and writes the files to the export folder. With --json, every command prints exactly one JSON document, failures included. The exit codes are designed for scripts: 3 means a human must answer a question or approval card, 4 means it timed out (the work keeps running), and 6 means team apply --check found drift.
Auth is careful: there is no --token flag “because a command line can be read by other programs”, tokens live in files, and CI tokens get an end date (openmausbot token create "Nightly CI" --scope client --expires 90d --out ci-token).
There is also a stdio MCP server, so Claude Desktop or Cursor can inspect bots, send work and wait for completion. It deliberately doesn’t expose approval grants, deletion, credentials or computer lifecycle. An outside agent can hand work to your team, but it cannot approve that work.
Adding your own engine
The three bundled drivers are not the limit. The custom engines doc shows two no-code routes in ~/.openmausbot/config.json: any CLI that speaks the Agent Client Protocol over stdio (a customAcp instance whose config.cli is the command to start), or any OpenAI-compatible endpoint, which covers OpenRouter, DeepSeek and local servers. Adding a first-class driver is, per the README, “one file in server/drivers/ plus a one-line registration”.
OpenMausBot vs Grok Bot and the closed agents
The project publishes its own Grok Bot vs MausBot comparison. It is a vendor page, so treat it as the maker’s framing, but it is unusually candid about where the closed product wins.
| Grok Bot (xAI) | OpenMausBot | |
|---|---|---|
| Price | Bundled with paid xAI / X plans | Free; you pay model providers directly |
| License | Proprietary | Apache-2.0 (plus enterprise/) |
| Model choice | Picked for you per task, no model picker | Claude, Codex, Grok or custom, per bot |
| Where agents run | One cloud computer per account | Your machine, on your CLIs |
| Where data lives | Vendor cloud | ~/.openmausbot on your disk |
| Keeps working with the laptop shut | Yes | No (unless you self-host on an always-on server) |
| Learns a task by watching you | Rolling out (“Teach a task”) | Not yet |
| Self-host / air-gap | No | Yes |
The two rows OpenMausBot concedes are real trade-offs of running locally: a bot on your laptop’s claude CLI stops when the laptop sleeps, unless you run openmausbot serve on a box that never does. Against Meta Muse, OpenAI dots and Cue by Manus, the pitch is the same: a team instead of one agent, your choice of model, no waitlist. If you want a self-improving single agent instead, we covered Hermes Agent. If what you want is the coding CLI underneath, see our Grok Build review.
Community reactions
The maker introduced the project on r/grok in mid-August (“I really liked the idea behind Grok Bot, so I decided to build my own open-source version”). Adafruit’s blog featured it on October 28. A run of “OpenMausBot beats Grok Bot” posts on r/AISEOInsider read as SEO content rather than user reports, so we gave them no weight.
The user feedback worth noting is mixed and mostly about polish. In r/GrokBot, one user wrote that on an Intel Mac OpenMausBot “seemed to cause spikes even when in the background,” and they moved to a different open-source project. The issue tracker shows the same kind of friction. Recent open issues include Codex being blocked at 100% subscription usage despite available credits (#4507), the Windows built-in browser repeatedly relaunching Chrome with a visible cmd window on 0.1.141 (#4572), and the iOS chat screen stuttering when scrolling (#4259). The longest-running thread, with 19 comments, is the staged Ubuntu desktop support plan (#29).
Honest limitations
- It is three months old and ships almost daily. 111 releases since August. v0.1.154 alone reorganized Settings and added streaming replies, Netlify publishing and a server updater. Expect the UI and flags to move under you.
- The backlog is large. 718 open issues against 514 closed. Some are feature plans, but many are platform bugs.
- Linux is a beta. Ubuntu 24.04 x64 is the only supported distro, GNOME is the supported desktop, local bot control works only on Xorg after explicit opt-in, and Wayland host control is disabled behind a safety gate.
- The Windows installer isn’t code-signed. SmartScreen will show “unknown publisher”.
- Some keys are stored in plaintext. The README says API keys entered through
openmausbot setupor the server path are saved unencrypted in a0600config.json. The packaged desktop app encrypts provider keys through the OS, but still keeps OpenCode provider keys, per-engine keys and MCP header values in plaintext in that file. - “Local-first” has paid edges. Cloud desktops come from Boat (paid after its trial), connected apps through a Composio account, and MausBot Cloud is a paid hosted plan. The core chat-with-your-CLIs loop is free.
- Open core. The
enterprise/folder needs a license key for production use. The OSS build is tested in CI without it. - Anonymous usage analytics are opt-out, in Settings → General.
- It inherits your agents’ limits. If your Claude plan rate-limits you, every Claude bot on your roster shares that limit. Five bots on one subscription is still one subscription.
FAQ
Is OpenMausBot free?
Yes. The app is free and Apache-2.0 licensed, apart from the source-available enterprise/ folder. You pay your model providers directly through the subscriptions behind your claude, codex or grok CLIs. Boat desktops, voice providers and MausBot Cloud cost extra.
Is OpenMausBot affiliated with xAI or Grok Bot?
No. The README says it is an independent project inspired by Grok Bot and not affiliated with xAI, Meta, OpenAI or Manus. It was called OpenGrokBot early on and now also goes by MausBot.
Do I need a Grok subscription to use it?
No. Any one of the claude, codex or grok CLIs, installed and logged in, is enough. You can also add an OpenAI-compatible endpoint or any ACP-speaking CLI as a custom engine.
Can OpenMausBot control my computer?
Only if you allow it. Bots can use a cloud desktop, an isolated local VM, or your own machine. Host control is supported on macOS and Windows, opt-in beta on Ubuntu Xorg, and disabled on Wayland. Shell commands and file edits surface as Allow / Deny cards either way.
Can I run it on a server instead of my laptop?
Yes. npx openmausbot serve runs the server on a VPS or always-on machine, reachable over Tailscale, your own reverse proxy, LAN or a hosted tunnel; devices pair with a one-time code. That is also how you get agents that keep working when your laptop is closed.
Where is my data stored?
Transcripts, events and settings live in ~/.openmausbot on the machine running the harness. Work done through connected apps or cloud desktops also passes through Composio and Boat.
Bottom line
OpenMausBot takes the agent-roster idea the big labs launched this autumn and moves the model, the machine and the data back to your side. The harness design is sound: one local server, one event stream, one permission broker. The headless CLI and MCP server are more thoughtful than most projects at this age. The cost is a codebase moving faster than its issue tracker can keep up with. Install it if you already live in two agent CLIs and want them on one team. Pin a version if you script against it.
Sources
- OpenMausBot repository and README
- OpenMausBot v0.1.154 release notes
- Run OpenMausBot from scripts and CI (headless CLI docs)
- Self-hosting the MausBot server
- Bring your own engine
- Connect apps through Composio
- LICENSING.md (Apache-2.0 and the enterprise carve-out)
- Grok Bot vs MausBot comparison (vendor page)
- openmausbot on npm
- Adafruit: OpenMausBot is an open-source Grok Bot alternative (October 28, 2026)
- r/grok: “I built an open-source Grok Bot alternative”