# MausBot Workspace for personal bot teams using agent CLIs, applications and controllable computers. Desktop, self-hosted servers and optional cloud run tasks and automations. Canonical profile: https://ki-agentenkompass.de/en/agents/openmausbot/ Editor: [Michael Meierhoff](https://ki-agentenkompass.de/en/about/) Sources reviewed: 2026-11-09 Basis: provider documentation. Examples are editorial suggestions, not hands-on product tests. ## Overview Independent project inspired by Grok Bot; connects existing agents rather than supplying its own model family. The website now uses MausBot. - Provider: Supamaus Software Private Limited - Product family: MausBot - Profile type: Agent workspace with desktop, self-hosting and optional cloud - Environment: Desktop on macOS, Windows and Ubuntu; optional self-hosted server or MausBot Cloud. Bots can use the host, a local VM or a remote desktop. - Connections: Gmail, GitHub, Slack, Notion and other services through Composio; supported agents receive file, terminal and computer tools. - Setup: Install the app and sign in to a supported agent engine or configure API access. Then choose a bot, working folder, tools and access mode. - Pricing model: Local app is free; AI usage follows your provider account. Optional cloud plans start at USD 15 monthly; enterprise features require a separate license. ## Key features ### Bots with individual roles Profiles, threads and groups organize work; delegation returns results to the originating chat. Source: https://docs.openmausbot.com/docs/features/bots-and-tasks ### Choose providers per bot Supported CLIs and API engines can be configured per bot; existing accounts determine model access and billing. Source: https://docs.openmausbot.com/docs/providers ### Assign a computer Host, local VM or cloud desktop is selected per bot; preview and takeover support supervision. Source: https://docs.openmausbot.com/docs/computers ### Connect applications OAuth connections expose tools for connected services to supported engines. Source: https://docs.openmausbot.com/docs/connected-apps ### Automations with run history Schedules and webhooks start work; history distinguishes waiting, completed, failed and cancelled runs. Source: https://docs.openmausbot.com/docs/features/automation ## Example workflows ### Example: prepare inbox work - Your input: An authorized email account and a task to draft replies. - Possible result: A bot returns drafts and open questions in chat. - What to check: Review recipients, content and approvals before sending. ### Example: recurring project review - Your input: A working folder, review instructions and a schedule. - Possible result: The routine returns a report; optionally the preceding run report can be included. - What to check: Check run status, actual changes and error messages. ## Requirements and limits ### Your own AI access Requirement: Agents require suitable authentication or API keys; their quotas and provider fees still apply. Source: https://docs.openmausbot.com/docs/providers ### Local execution needs a running host Requirement: Local routines and webhooks work only while the application runs; continuous operation requires a server or cloud. Source: https://docs.openmausbot.com/docs/features/automation ### Permissions vary by engine Limitation: Approval cards depend on engine and access mode; own profile and memory changes may apply immediately with Undo. Source: https://docs.openmausbot.com/docs/features/approvals-and-inspector ## A good fit if … - you want to use existing AI accounts through a shared bot interface. - you want to combine recurring work with files, services and computers. - you want to manage bot memories as editable local files. ## Less suitable if … - you expect every AI model without additional accounts or usage charges. - you need continuous local execution while your computer is off. - you expect identical approval and computer capabilities across every engine. Editorial assessment based on provider documentation. Not a product test. ## Usable AI models Open choice Choose through existing agent CLIs, API engines and compatible endpoints; OpenRouter and local models are documented. - Model families named: Anthropic (Claude), OpenAI (GPT), xAI (Grok), Google (Gemini), Moonshot (Kimi), Mistral, Alibaba (Qwen), DeepSeek · Other models can be connected freely - Model choice: You choose - Your own API key: Yes - Router or custom endpoint: Yes - Local models: Yes Documented · Sources accessed on: 2026-11-09 - [MausBot · Providers](https://docs.openmausbot.com/docs/providers) - [MausBot · Models](https://docs.openmausbot.com/docs/providers/model-providers) ## Europe & regional availability Product access, country availability and data processing are assessed separately. Reviewed scope: MausBot · Documented product access Reviewed on: 2026-11-09 ### Access and regional conditions With requirements Downloads for macOS, Windows and Ubuntu are documented. The inspected sources do not provide a complete country-availability list for cloud and connected providers. Region covered: EU/EEA, United Kingdom and Switzerland Documented reason: The conditions of the specific access route and connected services apply. Official source: https://docs.openmausbot.com/docs/getting-started/installation Official source: https://mausbot.com/pricing ## Accounts & permissions Based on provider documentation. Permissions depend on the account, integration and organization policies. Review the permissions actually requested before use. Configuration covered: MausBot · Account and permissions Sources reviewed: 2026-11-09 ### Account used Documented: Bots have their own profiles and working folders; a role does not create an additional provider subscription. Provider logins and API keys determine the AI identity used. Connected services use explicitly authorized accounts. Evidence: https://docs.openmausbot.com/docs/features/bots-and-tasks Evidence: https://docs.openmausbot.com/docs/providers Evidence: https://docs.openmausbot.com/docs/connected-apps ### Admin approval Documented with conditions: Supported engines display approvals and denials as conversation cards. Own profile, model and memory can change directly; details and Undo make this traceable. Desktop preview grants no control permission; host control requires separate authorization. Evidence: https://docs.openmausbot.com/docs/features/approvals-and-inspector Evidence: https://docs.openmausbot.com/docs/computers ### Data access & team sharing Documented with conditions: Connected services and files are accessible through their respective tools. Bots can operate a selected host, local VM or remote desktop. A working folder is not an operating-system sandbox. Evidence: https://docs.openmausbot.com/docs/connected-apps Evidence: https://docs.openmausbot.com/docs/computers Evidence: https://docs.openmausbot.com/docs/features/bots-and-tasks ## Prices and included usage Pricing checked: 2026-11-09 Local app is free; AI usage follows your provider account. Optional cloud plans start at USD 15 monthly; enterprise features require a separate license. ### Free USD 0 Local app; your own AI accounts and any service charges. Price source: https://mausbot.com/pricing ### Starter USD 15/month Dedicated cloud, 100 computer-hours per month. Price source: https://mausbot.com/pricing ### Pro USD 49/month Cloud, 300 computer-hours and USD 10 Claude credit per month. Price source: https://mausbot.com/pricing ### Max USD 99/month Cloud, 800 computer-hours and USD 20 Claude credit per month. Price source: https://mausbot.com/pricing Pricing details: https://mausbot.com/pricing ## Operation & oversight Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured. Deployment covered: MausBot · Execution and resumption Sources reviewed: 2026-11-09 ### Files and working state Documented: Configuration, transcripts, attachments and the SQLite message store reside in the executing host’s data directory. Evidence: https://docs.openmausbot.com/docs/self-hosting/data-and-backups ### Sign-ins Documented with conditions: Website sign-in can use takeover; saved logins can fill matching sign-in forms. Evidence: https://docs.openmausbot.com/docs/computers ### Starting further runs Documented: Chat, schedules and webhooks are documented triggers; local execution requires the app to run. Evidence: https://docs.openmausbot.com/docs/features/automation ### Human intervention Documented: Each thread has Stop; questions and approvals can be answered in conversation. Evidence: https://docs.openmausbot.com/docs/features/bots-and-tasks ### Detecting errors Documented with conditions: Run logs show failures and required actions; supported quota cases can run again later. Evidence: https://docs.openmausbot.com/docs/features/automation ### Resuming after failures Documented with conditions: Saved threads remain available. Backup restoration pauses routines and does not automatically replay unfinished delegation. Evidence: https://docs.openmausbot.com/docs/self-hosting/data-and-backups ### Editorial assessment Editorial assessment for the documented access route. Each criterion lists requirements and unresolved operating details. ## Memory and conversation continuity Scope: Bot files, shared threads and separate personal preferences Sources accessed: 2026-11-09 Editable Markdown memories with automatic upkeep and selective retrieval. ### Storage and scope Documented: Bot memories reside under ~/.openmausbot/workspaces//; backups include memory separately from saved credentials. - [MausBot · Memory](https://raw.githubusercontent.com/milind-soni/OpenMausBot/main/docs/memory.md) - [MausBot · Backup](https://docs.openmausbot.com/docs/self-hosting/data-and-backups) ### Selection and timing Documented: Enabled upkeep extracts after two idle minutes or six turns; explicit remember requests write during the turn. - [MausBot · Memory](https://raw.githubusercontent.com/milind-soni/OpenMausBot/main/docs/memory.md) ### Inspect, edit and delete Documented: The memory panel and files support editing, forgetting and Undo; MEMORY.md can be emptied. - [MausBot · Memory](https://raw.githubusercontent.com/milind-soni/OpenMausBot/main/docs/memory.md) ### Agent and channel boundaries Documented: Threads share bot memory; folders are not privacy boundaries. Personal preferences can apply across bots. - [MausBot · Bots](https://docs.openmausbot.com/docs/features/bots-and-tasks) - [MausBot · Memory](https://raw.githubusercontent.com/milind-soni/OpenMausBot/main/docs/memory.md) ### Retrieval Documented: A bounded MEMORY.md prefix loads each turn; word matching adds relevant topics and permitted conversation excerpts. - [MausBot · Memory](https://raw.githubusercontent.com/milind-soni/OpenMausBot/main/docs/memory.md) ### Session reset and compaction Documented: Files survive threads. Context compaction uses summaries or excerpts depending on the engine and optional helper model. - [MausBot · Bots](https://docs.openmausbot.com/docs/features/bots-and-tasks) - [MausBot · Memory](https://raw.githubusercontent.com/milind-soni/OpenMausBot/main/docs/memory.md) ## Context Agents require suitable authentication or API keys; their quotas and provider fees still apply. Official product documentation reviewed. Workflows and assessments are editorial; hands-on product tests are outside the scope of this directory. ## Sources - https://mausbot.com/ - https://docs.openmausbot.com/docs - https://docs.openmausbot.com/docs/getting-started/installation - https://docs.openmausbot.com/docs/features/bots-and-tasks - https://docs.openmausbot.com/docs/providers - https://docs.openmausbot.com/docs/providers/model-providers - https://docs.openmausbot.com/docs/connected-apps - https://docs.openmausbot.com/docs/computers - https://docs.openmausbot.com/docs/features/approvals-and-inspector - https://docs.openmausbot.com/docs/features/automation - https://raw.githubusercontent.com/milind-soni/OpenMausBot/main/docs/memory.md - https://docs.openmausbot.com/docs/self-hosting/data-and-backups - https://mausbot.com/pricing - https://docs.openmausbot.com/docs/changelog - https://github.com/milind-soni/OpenMausBot - https://raw.githubusercontent.com/milind-soni/OpenMausBot/main/LICENSING.md ## Provider The website names Supamaus Software Private Limited and creators Omkar Satpute and Milind Soni. The primary repository is milind-soni/OpenMausBot. - Operator: Supamaus Software Private Limited - Organization: Software provider - Website: https://mausbot.com/ - Reviewed: 2026-11-09 - Provider source: https://mausbot.com/ [Sources and method](https://ki-agentenkompass.de/en/sources/)