OpenMausBot: Claude, Codex as Persistent AI Bots (Grok Bot Alternative)

Create dedicated bots for coding, research, and operations, each with its own history, model, tools, approvals, and optional computer access.

OpenMausBot is a free, open-source desktop app that organizes Claude Code, Codex, Grok, and other AI agents as persistent bots just like Grok Bot, Claude Duet, and OpenAI Dots.

Each bot has its own role, model, instructions, and conversation threads, ready to pick up when you return.

For example, a repository bot can return to unfinished issues, a research bot can continue gathering sources, and an operations bot can work in connected apps.

You can bring bots into shared Rooms, assign recurring work, and follow their progress on your phone.

Key Features

  • Create persistent bots with their own agent, instructions, working folders, memory, and conversation threads.
  • Connect Claude Code, Codex, Grok, OpenCode, and other supported engines, with backup AIs for interrupted work.
  • Coordinate bots in Rooms, delegate work through a Chief of Staff, and share specific bots with teammates.
  • Split large assignments into parallel subtasks with Burst mode and receive a combined result.
  • Create automations in chat using schedules, webhooks, or connected-app events.
  • Connect Gmail, GitHub, Notion, Slack, and other services through Composio.
  • Use browser tools, cloud desktops, or an approved local computer to complete hands-on tasks.
  • Reuse Agent Skills and, on supported Macs, save repeatable computer steps.
  • Preview and publish pages that bots create directly from the conversation.
  • Access bots on Android, iOS, or a phone web app and inspect job activity and usage.
  • Run the free desktop app locally or move bots to an always-on cloud or team workspace.

OpenMausBot vs. Grok Bot

OpenMausBot is a free open-source alternative to xAI’s Grok Bot. Both organize persistent AI bots in a chat app. OpenMausBot uses your own AI accounts, a self-hosted server, or a MausBot Cloud workspace. Grok Bot uses Grok-powered bots on xAI infrastructure.

OpenMausBot (MausBot)Grok Bot
LicenseFree desktop app, Apache 2.0Proprietary managed service
ModelsClaude, Codex, Grok, and moreGrok models
ExecutionLocal host, self-hosted server, or paid CloudxAI-managed cloud
ComputersBot browser, optional remote desktop, local controlManaged bot computer
Team chatsRooms, delegation, team sharing permissionsGroup and team bots
Scheduled jobsSchedules, webhooks, app events; optional CloudCloud routines
Mobile accessAndroid/iOS companions and mobile web appMobile apps

How the Bots Work

Create a bot, define its role, select an AI, and send a request in chat. Its instructions and conversation threads persist across sessions. Return to a thread for unfinished work or start a separate conversation. New installations also include a MausBot helper that can set up bots, connected apps, and automations from your requests. Bot replies stream as they are written, including in Rooms.

Chats stay organized under their bots in the sidebar. You can pin a frequent conversation, rename a thread, duplicate a bot, archive past work, or search for an earlier discussion. Create separate local workspaces for work or personal bots, chats, and files. Only one local workspace runs at a time.

OpenMausBot Bots

Agents and Model Selection

OpenMausBot can run on most major AI coding agents like Claude Code, Codex, Grok, OpenCode, and DeepSeek Harness. It also supports Cline through ACP, Groq and OpenAI-compatible API endpoints, and Muse models through the Meta Model API.

MausBot detects a running local Ollama server, lists its downloaded models, and lets you adjust their thinking levels. Other supported options include Kiro and Claude through Amazon Bedrock. OpenAI and OpenRouter API models have selectable reasoning levels, and the model catalog refreshes automatically.

Assign an AI and model to each bot, or switch them during an existing conversation. Each bot can also have backup AIs, including a specific backup model. If an AI reaches a usage limit, MausBot can continue with a configured backup and return to the preferred AI after its limit resets. Usage-based API models take over only when you explicitly configure them as backups.

OpenMausBot Select Model

Example Bot Roles

  • Repository bot: investigate issues, edit code, inspect pull requests, and prepare release work.
  • Research bot: track a topic, collect source material, and organize findings.
  • Operations bot: work through connected email, calendars, Slack, Notion, or Linear.
  • Browser bot: complete web tasks using a browser or an available computer.
  • Review bot: examine another agent’s result using a different model.

Rooms, Teams, and Shared Work

Rooms let several bots work in a shared conversation. Mention a bot with @ to direct a request, or ask a Chief of Staff to assign parts of a larger job. Channels organize work by topic or project with their own conversations, instructions, working folders, and bot members. A bot can also hand work to another bot outside its current Room.

For a larger assignment, enter /burst or accept a bot’s suggestion. MausBot previews the subtasks, runs them in parallel, and combines their results. All plans include Burst mode, with greater concurrency on higher plans.

A Chief of Staff can create specialist bots, delegate jobs, and report on their progress. Its daily brief highlights outstanding approvals, failed automations, and other items needing attention. Delegated work can resume after a restart or approval.

You can also import a prepared team from a Markdown playbook or share one you built. A shared package can contain bot profiles, instructions, skills, Rooms, and routine definitions.

Paid Team workspaces add shared bots and human teammates. Open a bot’s Share menu to grant selected teammates view, chat, or edit access. Each person can also have a private conversation with a shared bot. Team connections can be shared across the organization or kept separately for individual members.

Automations, Triggers, and Agent Skills

Automations can run at a scheduled time, on repeating days, after an incoming webhook, or when a connected app reports an event. Ask a bot in ordinary language, such as “Every weekday at 9, summarize my inbox,” and it can create the automation and show controls to pause, edit, or undo it. Results arrive in that bot’s chat with an option to inspect the full run.

A bot can also wait for a reply, a page change, or a specified time using a “tell me when” request. MausBot monitors the condition and wakes the bot when it happens, conserving AI usage during the wait.

Local automations need their host online. An always-on Cloud or self-hosted server can run them after your laptop shuts down.

Agent Skills store instructions for recurring tasks. Create or import a skill, use an existing skill through chat, or let a Claude or Codex bot capture a successful series of actions. On a Mac, MausBot can also save the steps from a completed computer task and repeat them later with no AI call.

Connected Apps and Website Sign-ins

Composio connects bots to external apps such as Gmail, GitHub, Slack, Notion, and Linear. Authorize an account, and the bot can use the available actions, such as searching email, drafting replies, or working with calendar events.

For a site requiring login, the bot displays a Sign in needed card. Sign in within its browser, then select Done or reply “done” in chat. You can also save a site login or connect 1Password through a service account.

ConnectionWhen it is needed
Agent provider login or API keyTo run the selected Claude, Codex, Grok, or other engine
Composio account/keyTo give bots access to connected external apps
Boat account/keyTo use an independently provisioned remote cloud computer
1Password service accountOptional saved website logins
OpenMausBot Connected App

Computer and Browser Access

Bots use browser tools to navigate websites, fill in forms, and research online. For desktop tasks, assign a connected cloud desktop, an isolated private desktop, or an approved local computer. The Screen panel displays the bot’s desktop, and Take control lets you click and type in supported remote desktops before returning control to the bot.

On macOS, bots can use local screen capture and computer control after you grant permission. You can also lend your Mac’s apps, terminal, or Chrome session to bots running in your Cloud. Recent Windows builds support lending the computer’s apps and screen as well. On Ubuntu GNOME, preview works with Xorg or Wayland, but local host control requires explicit permission and Xorg.

OpenMausBot Computer

Create and Share Pages in Chat

When a bot builds a web page or dashboard, MausBot places a preview card in its conversation. Use Point to identify an element you want changed, open the page full screen, or move between earlier versions. The Share action publishes the result to a mausbot.page link. Bots can also deploy sites and web apps to your Netlify account or use hosting included with a Cloud plan. The Published apps view lists deployments with previews and a Delete control.

Run History and Usage

The Usage page shows which bots and models consumed time or paid AI usage. Open an individual run to review its steps, delegated work, duration, and recorded cost, or export the history as CSV. Each bot also reports its current step during longer tasks.

Data Analysis and Voice

In the Data tab, each bot has a local DuckDB database for working with files and database tables. Ask the bot to run SQL, inspect the result as a table or chart, and edit a query when needed. Earlier results stay accessible in the panel’s History.

Bots can read replies aloud through ElevenLabs, Fish Audio, xAI speech, built-in Mac voices, or a local Chatterbox server. On macOS, a live call lets you talk with a bot and hear its progress or approval requests.

Live calls use your own OpenAI API key. The paid Cloud tiers include monthly voice-reply allowances for spoken messages.

Give a bot a Google Meet, Microsoft Teams, or Jitsi link to have it join as a guest and take meeting notes. After the call, it posts a transcript, summary, decisions, and action items. Cloud plans include transcription. Local or self-hosted installations use a supported transcription API key or a local Whisper model.

Approval Cards

An AI engine can show an approval card when a tool needs permission. Approve, deny, or answer its question directly in chat. For a question with fixed choices, tap one of the options. Changes to bot and team setup can show an Undo action. The engine’s own permission rules continue to apply.

The Chief of Staff shows which teammate needs a decision and can resume delegation after you respond. In a Team workspace, bot access and sharing permissions also determine who can view, chat with, or edit a shared bot.

Getting Started

Download the free desktop app for your device. The initial setup checks for a compatible AI engine and helps you sign in. The new-workspace helper can configure your first bot. You can also create one manually and give it a task immediately.

macOS

  1. Download the installer for Apple silicon or Intel.
  2. Drag OpenMausBot from the .dmg into Applications and open it.
  3. Connect Claude, Codex, Grok, or another available provider.
  4. Create a bot, select a model, and send a task.

Windows

  1. Download the 64-bit .exe installer and run it.
  2. If SmartScreen shows an unknown-publisher warning, verify the installer source before proceeding. Windows signing is not yet complete.
  3. Connect an AI provider, create a bot, and select a model.

Linux

For Ubuntu 24.04 x86-64, download the .deb package or AppImage. The .deb is the recommended browser-ready installation for Ubuntu GNOME. Other Linux distributions can try the AppImage.

sudo apt install ./OpenMausBot-amd64.deb

Run From Source

Install Node.js, pnpm, and an agent CLI. Clone the repository and install dependencies:

git clone https://github.com/milind-soni/OpenMausBot.git
cd OpenMausBot
pnpm install

Run the following development processes in three terminals from the repository directory. Keep the server and web app running when you launch Electron.

TerminalCommand
1. Harness serverpnpm dev:server
2. Web apppnpm dev
3. Electron apppnpm dev:desktop

Run From the Terminal

Launch it and follow the prompts to sign in to an AI engine, select a model, and optionally pair a phone. Run openmausbot setup to change the saved setup later.

npx openmausbot

Use It From Your Phone

Android (8.0+) and iOS (17.0+) companion apps connect to your running computer or server. You can also add the phone web app to your home screen. Pair the phone with a running, remotely reachable host to use its bots and respond to approvals. A self-hosted server can use MausBot’s relay for phone pairing with --relay, with no public domain or open port.

How OpenMausBot Works Behind the App

OpenMausBot uses React and Electron for its desktop app. A local harness launches agent processes and delivers chat messages, tool activity, and approval requests through an event stream. In development, the harness listens at 127.0.0.1:8799. An optional MCP server lets external clients such as Claude Desktop and Cursor inspect bots, send tasks, and manage selected team actions. The openmausbot CLI can also apply a team definition, run a bot from scripts or CI, wait for delegated work, and export artifacts.

ComponentRole
Agent driversConnect to individual CLIs and provider protocols
Harness and event streamRun agents and deliver messages, tools, and approvals
React / Electron appDisplay chats, teams, settings, and computer activity
MCP serverLet compatible external clients manage a bounded set of bot and team actions

Free Desktop App, Cloud Plans, and Costs

The desktop app is free and Apache 2.0 licensed. MausBot Cloud adds an always-on host, cloud-desktop time, connected-app allowances, and voice replies.

Individual Cloud plans include 2,000 connected-app events per day. Starter allows unlimited bots, with five awake and two working simultaneously. Pro includes $10 and Max includes $20 of Claude credit per month; Starter uses your own AI account or key.

For organizations, the Team plan is $169 per month for up to five people, with shared bots and 1,000 cloud computer-hours. Business costs $599 per month for up to 20 people and 3,000 hours, and Business self-hosted starts at $299 per month on your own servers.

PlanMonthly priceCloud computer-hours/month
Free desktop$0Not included
Starter$15100
Pro$49300
Max$99800

Local Storage and Privacy

The local harness stores conversations and event data under ~/.openmausbot on your computer. The packaged desktop app encrypts AI provider and service keys through the operating system. CLI and server setup save API keys as plaintext in a private config.json file (0600 on Unix). The desktop config can also contain engine-specific keys and MCP headers in plaintext. A MausBot Cloud or Team workspace stores its hosted data on its own server.

AI prompts go to the model provider you connect. Connected apps and remote desktops process the information needed for their assigned tasks. In Team workspaces, a shared bot’s access can be limited separately for viewing, chatting, and editing. Each teammate’s private chats remain private.

Pros

  • Persistent bots with multiple models and individual conversation threads.
  • Team delegation, event-based automations, reusable Skills, and backup AIs.
  • Computer access and hundreds of connected app integrations.
  • Mobile companions, always-on Cloud hosting, and Team sharing permissions.
  • In-chat approvals, generated page previews, and detailed usage history.

Cons

  • Model usage needs a separate account, subscription, or API key.
  • Free local automations stop when their host sleeps or goes offline.

Alternatives & Related Resources

FAQs

Do I need a Grok subscription?

No. You can run bots through Claude Code, Codex, or another compatible agent engine using its own account or API credentials.

Can bots run when my computer is turned off?

Locally hosted bots and schedules stop when their host shuts down. You can keep them running on an always-on self-hosted server or a paid MausBot Cloud workspace.

Does every bot need Composio or a cloud computer?

No. A bot can run with an authenticated agent engine alone. Composio is optional for connections to external services, and a third-party cloud computer is only needed for tasks that require that remote desktop.

Last Updated: Nov 11, 2026

Leave a Reply

Your email address will not be published. Required fields are marked *

Get the latest & top AI tools sent directly to your email.

Subscribe now to explore the latest & top AI tools and resources, all in one convenient newsletter. No spam, we promise!