Who OpenMausBot is for#
Developers managing repetitive multi-step workflows
Run parallel Claude and Codex agents against GitHub, Gmail, and Notion without switching windows or restarting sessions. The permission broker surfaces shell commands and file edits as inline decisions so you stay in control as agents work through multi-step tasks.
Skip if:
You need agents running unattended 24/7 without the desktop app open. Webhooks require OpenMausBot to be running, so always-on automation needs an additional relay or hosting layer on top of the local install.
Technical teams with existing AI CLI subscriptions
If your team already holds Claude Code, Codex, or Grok subscriptions, OpenMausBot adds an agent management layer at no extra software cost. Each member runs their own local instance with their own credentials and no shared cloud account.
Skip if:
Your team needs a shared, centrally managed workspace with SSO and audit logs today. The Enterprise tier covers that path, but the current build runs per-user on individual machines rather than as a shared service.
Solo developers building calendar-scheduled automations
Set up bots on a day-of-week calendar schedule or trigger them from incoming webhooks. The permission broker handles approval flows inline, so you can supervise recurring agent tasks without writing custom guardrails or running a separate orchestration service.
Skip if:
You want a cloud-hosted, always-on automation platform with no local install. OpenMausBot is a desktop app and does not run agent workloads in the cloud without a self-hosted server arrangement.
The problem it solves#
Running multiple AI agents in parallel is a coordination problem. Switching between terminal sessions loses context from prior conversations, and re-authorizing tools for every session adds repetitive overhead. Most commercial agent platforms address this by routing all agent traffic through their own cloud, which adds a second subscription on top of the AI provider fees you already pay, while your data and credentials leave your machine in the process.
The alternative most developers reach for is custom scripts and wrappers, which work but require constant maintenance and give no oversight layer. There is no standard way to pause a running agent, approve a shell command before it executes, or hand work between agents without building that plumbing yourself. The gap between one-off chat sessions and a properly supervised multi-agent setup is exactly the problem OpenMausBot is designed to close.
How it solves it#
Messaging app UI for your agent team
Each bot appears as a chat contact in the sidebar. Right-click to pin, duplicate, hide, or delete bots the same way you manage contacts. Conversations persist per-thread, so an agent picks up where it left off without losing context between sessions.
Per-bot model selection with live switching
A model picker shows Claude and Codex providers side by side, with defaults marked and unavailable providers dimmed with a reason. Switch a bot's model mid-conversation without restarting it. Custom CLI binaries can be pointed at under Settings for versioned builds or wrappers.
Cloud computer and local computer use
Each bot can get a cloud Linux desktop that spins up on demand with a live screen preview while it works, or you can point the bot at your local Mac for computer use. Both paths share the same inline approval flow for risky actions before anything runs.
500+ connected apps via Composio
A one-click marketplace connects bots to Gmail, Slack, GitHub, Notion, Linear, and hundreds more through Composio. OAuth once per app; every bot can use those connections as tools without re-authenticating separately per bot.
Permission broker for agent actions
Shell commands, file edits, and questions surface as inline approval cards in the chat thread. Allow, deny, or respond in chat before the bot proceeds. The broker applies to both cloud and local computers, so no action runs silently.
Calendar routines and webhook triggers
Bots run on a day-of-week calendar schedule or fire from an incoming webhook. The webhook receiver runs on a dedicated local port (8800) separate from the main API, with Bearer authentication support. The scheduler puts routines on a calendar rather than a list.
Strengths and trade-offs#
Strengths
- No additional subscription feesBots run on the Claude, Codex, and Grok CLIs already installed on your machine, using your existing logins. OpenMausBot itself is free under MIT with no feature tiers. You pay only for the AI providers you already use, with no proxy markup on top.
- Fully local data storage by defaultTranscripts, API keys, and events live in ~/.openmausbot on your own disk. Nothing leaves your machine unless you send it. API keys are write-only in the UI: the interface only ever sees a configured flag, never the raw value.
- MIT license with no feature tiersThe entire app is MIT licensed. Every feature is available with no plan gating: unlimited bots, all providers, Composio connections, calendar routines, and webhook triggers. There is no paid tier that unlocks additional capabilities.
- Extensible driver architectureAdding a new AI provider is one file in server/drivers/ plus a one-line registration. The driver SPI in server/contracts.ts is deliberately small. Unknown drivers degrade to unavailable status in the model picker without crashing the rest of the running fleet.
Trade-offs
- -Voice calls are macOS-onlyThe call feature rides on-device Apple speech recognition, which is macOS-only in the current build. On Windows and Ubuntu you get text chat, streamed replies, and ElevenLabs text-to-speech readback, but not two-way voice calls. The README notes calls depend on the same on-device dictation path as the composer mic.
- -Ubuntu support is in beta with capability limitsUbuntu 24.04 x64 packages are in beta. Local screen preview, computer-use automation, on-device dictation, and ARM64 are not yet available on Linux. Composio app connections and cloud computer access via Box work, but direct local desktop control is planned rather than shipping.
- -Webhooks require the app to be runningThe webhook receiver at 127.0.0.1:8800 only works while OpenMausBot is open. For public internet delivery you need a relay such as Tailscale Funnel. There is no always-on hosted relay yet, so unattended overnight automation needs an extra hosting layer.
- -Cloud computer and Composio are third-party paid servicesBox (the cloud computer provider) and Composio each have their own accounts and terms. Box is a paid service after its free trial, so heavy use of per-bot remote desktops can add costs outside OpenMausBot itself. Local agent chat works without either service.
OpenMausBot vs alternatives#
OpenMausBot vs Grok Bot
OpenMausBot was built as a direct open-source answer to Grok Bot, xAI's proprietary agent platform. Both organize AI agents as a roster of chat contacts, each with its own model, apps, and computer. The key decision point is where agents run and who controls the costs.
| Feature | OpenMausBot | Grok Bot |
|---|---|---|
| License | MIT (open source) | Proprietary |
| Agent runtime | Your machine (Claude, Codex, Grok CLIs) | xAI-hosted cloud |
| Data storage | ~/.openmausbot, local disk | xAI cloud |
| Self-hosting | Yes, desktop app with embedded server | No |
| Cost | Free software; your existing CLI subscriptions | Subscription required |
OpenMausBot is the stronger choice when you want agent data to stay on your machine, want to reuse CLI subscriptions you already have, or need agents with direct access to your local file system and macOS desktop. Grok Bot has an advantage for teams that want a fully managed cloud experience with no local install, and for users who do not already hold Claude or Codex subscriptions.
OpenMausBot vs Lindy AI
Lindy AI is a commercial cloud-based agent platform targeting business teams who want workflow automation without a local install. OpenMausBot takes a different approach: local-first desktop agents built for developers, running on models you already own.
| Feature | OpenMausBot | Lindy AI |
|---|---|---|
| License | MIT (open source) | Proprietary |
| Deployment | Local desktop app | Cloud SaaS |
| Data storage | Local disk (~/.openmausbot) | Vendor cloud |
| Agent model | Bring your own CLI (Claude, Codex, Grok) | Platform-managed |
| Self-hosting | Yes | No |
| Cost | Free software; your existing CLI subscriptions | Paid subscription |
OpenMausBot fits developers and technical teams who prefer to keep data local, want to bring their own AI models, and are comfortable with a CLI-native setup. Lindy AI is better suited for non-technical business users who want a cloud-hosted workflow builder with no local install or CLI familiarity required.
Install and self-host#
Install from source on macOS, Windows, or Ubuntu 24.04 with Node 24 and pnpm; released desktop builds for macOS and Windows embed the server and need no separate setup.
```bash
git clone https://github.com/milind-soni/OpenMausBot
cd OpenMausBot
pnpm install
pnpm dev:server
pnpm dev
```What it's built on#
- Languages
- JavaScriptSwiftTypeScript
- Frameworks
- React
- Tooling
- esbuild
FAQ#
Is OpenMausBot free to use?
Yes. The full app is MIT licensed and free forever with no feature tiers. You need existing subscriptions to Claude, Codex, or Grok to run their respective CLIs. The optional cloud computer (Box by ascii.dev) is a paid service after its trial, and Composio has its own account and pricing above the free tier. The OpenMausBot software itself carries no subscription.
Which AI models does OpenMausBot support?
It supports Claude (via the claude CLI), Codex (via the codex CLI), and Grok (via the grok CLI). Each must be installed and authenticated on your machine; they appear in the model picker automatically once detected. You can also point any bot at a custom CLI binary in Settings under Engines, which allows versioned builds or wrappers for other providers.
Which platforms does OpenMausBot support?
macOS (Apple silicon, signed and notarized) and Windows (64-bit, one-click installer with no admin rights needed) have released desktop builds with the harness server embedded. Ubuntu 24.04 x64 packages are in beta, with local screen capture and computer control not yet available. iOS is listed as not yet available on the product website.
How is OpenMausBot different from Grok Bot?
Grok Bot is xAI's proprietary agent platform. OpenMausBot is an independent open-source project inspired by the same concept: AI agents organized as chat contacts with their own models, computers, and apps. OpenMausBot runs on the CLI agents you already have, stores everything locally in ~/.openmausbot, and costs nothing beyond your existing AI subscriptions. It is not affiliated with or endorsed by xAI.
Can I add a custom AI provider or agent CLI to OpenMausBot?
Yes. The driver SPI in server/contracts.ts is deliberately small, and adding a provider is one file in server/drivers/ plus a one-line registration. Unknown or unsupported drivers degrade to unavailable status in the model picker without crashing other running bots in the fleet.
Similar open-source tools#
rakazo
AI teammates you own: your keys, your model, your machine.
Hermes Agent
Self-hosted AI agent with persistent memory, multi-channel chat, and model choice across OpenAI, OpenRouter, and custom endpoints.
vexa
Self-hosted meeting bot API for Meet, Teams, Zoom, and Jitsi
LiveCaptions-Translator
Real-time audio translation for Windows, powered by LLMs
whishper
Local speech-to-text transcription and subtitling with a web UI
CLI-Anything
Empower AI agents with agent-native CLIs