# OpenMausBot vs Paseo (slim)

> OpenMausBot scores 65.4 (B) to Paseo's 62.1 (B) for multi-agent orchestration. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/openmausbot-vs-paseo.md (~5,500 tokens) · this version ~2,030 tokens · JSON https://www.anchorterminal.com/compare/openmausbot-vs-paseo.json · canonical https://www.anchorterminal.com/compare/openmausbot-vs-paseo
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

OpenMausBot scores 65.4 (B) on agent readiness against Paseo's 62.1 (B), and leads in 4 of 7 scored categories. Paseo leads on payments & pricing and transparency & trust. Both do multi-agent orchestration.

- OpenMausBot: B 65.4, rank #424 of 1510 · https://www.anchorterminal.com/tools/openmausbot.min.md
- Paseo: B 62.1, rank #577 of 1510 · https://www.anchorterminal.com/tools/paseo.min.md
- OpenMausBot, good for A person or an outside agent who wants several CLI agents (Claude Code, Codex, Grok, ACP CLIs) organised as named bots with their own computers, routines and approvals, driven by MCP or a CLI. Ahead on Reliability, 60 against 50; Schema & documentation, 90 against 65; Agent ergonomics, 77 against 70. Also Runs on your own machine; Free to start without a card.
- Paseo, good for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere. Ahead on Payments & pricing, 60 against 50; Transparency & trust, 68 against 59. Also No key needed to call it.

| Category | OpenMausBot | Paseo |
| --- | --- | --- |
| Reliability (16%) | 60 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 90 | 65 |
| Agent ergonomics (13%) | 77 | 70 |
| Security & auth (14%) | 59 | 58 |
| Payments & pricing (10%) | 50 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 74 | 75 |
| Transparency & trust (7%) | 59 | 68 |

| Fact (where they differ) | OpenMausBot | Paseo |
| --- | --- | --- |
| Vendor | Supamaus Software Private Limited | Mohamed Boudra |
| Transports | stdio |  |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| Tools exposed | 20 | none |
| Last release | 2026-11-01 | 2026-11-07 |
| Terms last updated | 2026-10-10 | no document linked |
| Privacy policy last updated | 2026-10-18 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 8.2k stars, 3.5k npm/wk | none |

Why the edge:
- Schema & documentation, OpenMausBot +25: OpenMausBot 90 (The MCP server's 20 tools each have a JSON Schema input with `additionalProperties: false` and required fields marked. No OpenAPI for the local HTTP API (25). Markdown docs in the repository, and the docs app's source serves llms.txt, llms-full.txt and Markdown routes. docs.openmausbot.com disallows every crawler, so the live llms.txt was not read (10). Descriptions state purpose and limits, such as that `update_bot_profile` cannot alter permissions, that `send_bot_message` may make the bot use external tools and that `edit_bot_message` is refused while a thread works, and the server instructions say to read before mutating. Few say when not to use a tool (15). Integer limits with minimum and maximum, an enum on `scope`, a pattern on `send_id` and `oneOf` shapes for responders (13). JSON configuration examples for each install path, the wait statuses and job states, CLI exit codes and a `{ ok, error, hint, exitCode }` failure shape (12). MCP server version 1.1.0, release notes per version and a changelog page in the docs (15).); Paseo 65 (Harness reading. Public docs, a CLI and plugin examples in the repository (65).)
- Reliability, OpenMausBot +10: OpenMausBot 60 (Read as local software. Official npm package `openmausbot` (Node.js 24 or newer) and signed, notarised macOS builds, a Windows installer and Ubuntu 24.04 packages, with supported platforms and a capability table in the README (20). 2,075 test files and a CI workflow on main. Of the last 23 finished CI runs on main on 30 October 2026, 10 passed, 3 failed and 10 were cancelled by newer pushes in a serialised queue (20). 365 open issues against about 3,940 issues and pull requests filed since 11 August, so most are closed, but the 25 newest open issues include several bug reports from 29 and 30 October with no reply yet (15). Release notes for every version in New, Easier and Fixed sections, but new capabilities ship in 0.1.x patch versions and no release marks breaking changes (5). Version 0.1.134, and the README calls the project early (0).); Paseo 50 (Local software. Desktop builds, an Android APK, a Docker image and a Nix package (20). ci.yml on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Version 0.15.3 (0). 20 + 15 + 0 + 15 + 0 = 50.)
- Payments & pricing, Paseo +10: OpenMausBot 50 (No payment protocol (0). MausBot Cloud, the hosted option, is priced by plan on a public page ($15, $49 and $99 a month, Team $169 and Business $599, or Business self-hosted $299 a month billed yearly, re-read on 2 November), with extra computer-hours at $0.05 each, so plan pricing (10). The app is free with no card or account (20). `npx openmausbot` installs and starts it with no signup (20).); Paseo 60 (Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60.)
- Transparency & trust, Paseo +9: OpenMausBot 59 (Apache 2.0 outside `enterprise/`, which is source-available and needs a licence key in production. Deleting the folder leaves the open-source edition, and a CI job builds it (27). The privacy policy of 18 October 2026 (re-read on 2 November, unchanged) names Supamaus Software Private Limited and separates the local apps from the optional hosted service, but it says the apps contain no third-party analytics SDKs while the app loads posthog-js by default, and hosted account data is kept while needed with no period stated (12). No deprecation policy. Dated release notes, and older installers kept in a legacy releases repository (4). docs/analytics.md lists every event and property and how to switch it off, but analytics are on by default and the privacy policy does not mention them for the apps (14).); Paseo 68 (Apache 2.0 for everything but third-party components (30). No telemetry and agents run on your machine (22 of 30). CHANGELOG.md, no deprecation policy (10). States no telemetry (20). 30 + 22 + 10 + 20 = 82.)
- Agent ergonomics, OpenMausBot +7: OpenMausBot 77 (20 tools, inside the 11 to 30 band, with annotations that separate reads from writes but no toolsets or read-only mode to load. Transcript reads are bounded and never return screenshot pixels (17). `limit` up to 200 messages, search capped at 100 hits, `task_id` and `scope` filters, and `since_ms` and `after_version` to keep watching a job (17). `wait_for_conversation` reports settled, needs-user, failed, stalled or timed-out with a redacted transcript tail, and the CLI's exit codes separate a pending approval from a timeout. We did not read every MCP error path (15). `send_id` makes a repeated send return the first receipt, `wait` is held by the server rather than polled, and every tool carries readOnlyHint, destructiveHint, idempotentHint and openWorldHint (20). Few required parameters and defaults for task, limit and timeout. The server answers only while the app or `openmausbot serve` runs, mutating tools need a paired token in packaged builds, and there is no client SDK beyond the CLI (8).); Paseo 70 (Harness reading. A self-hosted daemon that agents can use to create worktrees, launch other agents and talk to them, scriptable from the CLI (70).)