Skip to main content
Back

OpenMausBot Turns AI Agents Into a Messaging App With 500+ Connected Tools

OpenMausBot turns Claude Code and Codex CLIs into a chat app of AI agents, each with its own model, cloud computer, and connected apps.

Repo, Full Access
  • OpenMausBot is an open source Mac app that turns Claude and Codex CLIs into a roster of chat-style agents
  • Each bot gets its own personality, model, cloud Linux desktop, and connected app integrations
  • Local-first architecture: harness server on 127.0.0.1 owns agent processes, secrets stay on disk
  • Inline Allow/Deny approval cards gate every shell command, file edit, or risky action
  • 500+ integrations via Composio Connect, cloud computers via Box, computer use via trycua
  • Free, MIT licensed, uses your existing Claude and Codex subscriptions — repo here

A new open source project called OpenMausBot reframes AI agents as contacts in a messaging app. Instead of one chat window with one assistant, you get a sidebar full of bots, each running as a real agent process on your Mac with its own personality, model choice, cloud computer, and connected tools. The creator pitched it on X as an open source take on the Grok-style bot experience that piggybacks on the AI subscriptions you already pay for rather than adding another one.

The mental model is straightforward: every bot is a full agent session on Claude or Codex, with tools, files, and reasoning included, and you can switch a bot's model mid-conversation. You right-click a bot the way you would a contact in Telegram: pin, mark unread, edit profile, duplicate, hide, delete. The novelty lies in the shape of the interface wrapped around otherwise familiar agents.

Two processes, one event stream

Under the hood, OpenMausBot splits cleanly into an app and a harness server. The React app holds no transports itself, sending typed commands over HTTP and folding a single SSE event stream into state. A small harness server on 127.0.0.1:8799 owns every agent process and normalizes each provider's native protocol into one canonical event stream, logged per-thread as NDJSON.