What it does
5 features
MausBot · Agent workspace with desktop, self-hosting and optional cloud
Product and access
Independent project inspired by Grok Bot; connects existing agents rather than supplying its own model family. The website now uses MausBot.
Core features
5 features from provider sources · reviewed on November 9, 2026. Availability and limitations are listed directly below.
Bots with individual roles
Profiles, threads and groups organize work; delegation returns results to the originating chat.
Source 4Choose providers per bot
Supported CLIs and API engines can be configured per bot; existing accounts determine model access and billing.
Source 5Assign a computer
Host, local VM or cloud desktop is selected per bot; preview and takeover support supervision.
Source 8Connect applications
OAuth connections expose tools for connected services to supported engines.
Source 7Automations with run history
Schedules and webhooks start work; history distinguishes waiting, completed, failed and cancelled runs.
Source 10
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
The rating covers the generally available main access. Documented · Sources accessed on
Does it fit my task?
2 practical tasks · 3 requirements and limits
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.
Practical tasks
Editorial examples based on documented features. No product tests performed.
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.
Example: prepare inbox work
Your possible prompt
Compare three providers for [task]. Use their official documentation. Show differences, sources, and open questions in a table.
Adjust the task, data and permissions.
Requirements and limits
Requirement
Your own AI access
Agents require suitable authentication or API keys; their quotas and provider fees still apply.
Source 5Requirement
Local execution needs a running host
Local routines and webhooks work only while the application runs; continuous operation requires a server or cloud.
Source 10Limitation
Permissions vary by engine
Approval cards depend on engine and access mode; own profile and memory changes may apply immediately with Undo.
Source 9
Can I use it?
With requirements
Europe & regional availability
Product access, country availability and data processing are assessed separately.
Reviewed scope: MausBot · Documented product access
Reviewed on:
With requirements
Access and regional conditions
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, reason and source
Region covered: EU/EEA, United Kingdom and Switzerland
Documented reason: The conditions of the specific access route and connected services apply.
Official source · docs.openmausbot.com · Official source · mausbot.com
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:
Show all 3 points
Documented with conditions
Admin approval
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 · Evidence
Memory and conversation continuity
6 of 6 criteria documented
Editable Markdown memories with automatic upkeep and selective retrieval.
Bot files, shared threads and separate personal preferences
Sources accessed:
Documentation by criterion
StorageDocumented
Storage and scope
Bot memories reside under ~/.openmausbot/workspaces/<botId>/; backups include memory separately from saved credentials.
SelectionDocumented
Selection and timing
Enabled upkeep extracts after two idle minutes or six turns; explicit remember requests write during the turn.
Edit & deleteDocumented
Inspect, edit and delete
The memory panel and files support editing, forgetting and Undo; MEMORY.md can be emptied.
Access boundariesDocumented
Agent and channel boundaries
Threads share bot memory; folders are not privacy boundaries. Personal preferences can apply across bots.
RetrievalDocumented
Retrieval
A bounded MEMORY.md prefix loads each turn; word matching adds relevant topics and permitted conversation excerpts.
New conversationsDocumented
Session reset and compaction
Files survive threads. Context compaction uses summaries or excerpts depending on the engine and optional helper model.
Cost and effort
4 plans · Prices as of 9 November 2026
Prices and included usage
Pricing checked
Local app is free; AI usage follows your provider account. Optional cloud plans start at USD 15 monthly; enterprise features require a separate license.
| Plan | Price | Included |
|---|---|---|
| Free | USD 0 | Local app; your own AI accounts and any service charges. |
| Starter | USD 15/month | Dedicated cloud, 100 computer-hours per month. |
| Pro | USD 49/month | Cloud, 300 computer-hours and USD 10 Claude credit per month. |
| Max | USD 99/month | Cloud, 800 computer-hours and USD 20 Claude credit per month. |
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.
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:
Editorial assessment
Editorial assessment for the documented access route. Each criterion lists requirements and unresolved operating details.
Show all 6 points
Documented
Files and working state
Configuration, transcripts, attachments and the SQLite message store reside in the executing host’s data directory.
EvidenceDocumented with conditions
Sign-ins
Website sign-in can use takeover; saved logins can fill matching sign-in forms.
EvidenceDocumented
Starting further runs
Chat, schedules and webhooks are documented triggers; local execution requires the app to run.
EvidenceDocumented
Human intervention
Each thread has Stop; questions and approvals can be answered in conversation.
EvidenceDocumented with conditions
Detecting errors
Run logs show failures and required actions; supported quota cases can run again later.
EvidenceDocumented with conditions
Resuming after failures
Saved threads remain available. Backup restoration pauses routines and does not automatically replay unfinished delegation.
Evidence
Evidence and open questions
16 sources · 0 open points
Sources and evidence
Official product documentation reviewed. Workflows and assessments are editorial; hands-on product tests are outside the scope of this directory.
Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.
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
- mausbot.com
Changes to this profile 1
Workspace for personal bot teams using agent CLIs, applications and controllable computers. Desktop, self-hosted servers and optional cloud run tasks and automations.
These notes describe editorial changes. Source and pricing review dates appear in their respective sections.