# Conductor vs OpenMausBot (slim)

> OpenMausBot scores 65.4 (B) to Conductor's 41.3 (E) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/conductor-vs-openmausbot.md (~6,200 tokens) · this version ~2,530 tokens · JSON https://www.anchorterminal.com/compare/conductor-vs-openmausbot.json · canonical https://www.anchorterminal.com/compare/conductor-vs-openmausbot
- 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 Conductor's 41.3 (E), and leads in every scored category. Both do agent harnesses.

- Conductor: E 41.3, rank #1285 of 1486 · https://www.anchorterminal.com/tools/conductor.min.md
- OpenMausBot: B 65.4, rank #422 of 1486 · https://www.anchorterminal.com/tools/openmausbot.min.md
- Conductor, good for Existing Conductor users planning their move before Cloud closes on 20 November 2026 and the local app winds down in early 2027.
- 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 25; Schema & documentation, 90 against 60; Agent ergonomics, 77 against 55; Security & auth, 59 against 45; Payments & pricing, 50 against 0; Maintenance & community, 74 against 58; Transparency & trust, 59 against 53. Also Runs on your own machine; Free to start without a card; Open source.

| Category | Conductor | OpenMausBot |
| --- | --- | --- |
| Reliability (16%) | 25 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 60 | 90 |
| Agent ergonomics (13%) | 55 | 77 |
| Security & auth (14%) | 45 | 59 |
| Payments & pricing (10%) | 0 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 58 | 74 |
| Transparency & trust (7%) | 53 | 59 |

| Fact (where they differ) | Conductor | OpenMausBot |
| --- | --- | --- |
| Vendor | Conductor (joining Meta) | Supamaus Software Private Limited |
| Transports |  | stdio |
| Pricing | Paid | Freemium |
| Licence | Proprietary. A closed-source Mac app and hosted Conductor Cloud under Conductor's terms | Apache-2.0 |
| Tools exposed | none | 20 |
| Last release | 2026-11-04 | 2026-11-01 |
| Terms last updated | not read yet | 2026-10-10 |
| Privacy policy last updated | not read yet | 2026-10-18 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | none | 8.2k stars, 3.5k npm/wk |

Why the edge:
- Payments & pricing, OpenMausBot +50: Conductor 0 (No new sign-ups since 4 November, free users can't upgrade, and no price is shown. No protocol, no published price, no open free tier, no onboarding (0).); 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).)
- Reliability, OpenMausBot +35: Conductor 25 (Read as local software that is winding down. Installed from Conductor's own download, which stopped taking new users on 4 November 2026 (10). Closed source, so no public CI or issue tracker (0, 0). A dated changelog, newest 0.93.0 on 4 November (15). Version 0.93 (0). 10 + 0 + 0 + 15 + 0 = 25.); 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).)
- Schema & documentation, OpenMausBot +30: Conductor 60 (Harness reading. Docs for workspaces, review and merge, a Conductor API reference page linked from the docs (not read), and security and permissions pages (60).); 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).)
- Agent ergonomics, OpenMausBot +22: Conductor 55 (Harness reading. Each task gets a workspace, branch, terminal and diff, with pull requests and merges from the app, and an API for integrations; not re-read in detail (55).); 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).)
- Maintenance & community, OpenMausBot +16: Conductor 58 (0.93.0 on 4 November 2026 (30). Several dated releases in 90 days, per the changelog index (20). Discord, a subreddit and email for support (8). Closed app, no package or CI to read (0). 30 + 20 + 8 + 0 + 0 = 58. The local app gets new models and critical fixes only until early 2027.); OpenMausBot 74 (v0.1.137 on 1 November 2026, after v0.1.135 on 31 October and v0.1.136 on 1 November (30). 128 desktop versions from 11 August to 30 October 2026, and three more since (20). The maintainer has 4,221 commits and the contributor list returns at least 100 accounts. 587 issues and pull requests were open from about 3,940 filed on 30 October, when we could only sample the newest open issues, nearly all from the last two days and mostly unanswered so far (per the 30 October check; github.com refuses our requests on 2 November) (16). Not in the official MCP registry, which returns nothing for mausbot (0). CI on main runs on every push with most finished runs passing, npm provenance and an SBOM for the bundled Cua runtime (per the 30 October check) (8). 30+20+16+0+8 = 74.)
- Security & auth, OpenMausBot +14: Conductor 45 (Closed app. Telemetry and data handling weren't read beyond the transition notice (10 of 30). A security and permissions page (10 of 20). No prompt-injection guidance found (5). No audit log found (5). SOC 2 Type II report at trust.conductor.build (15 of 20). 10 + 10 + 5 + 5 + 15 = 45.); OpenMausBot 59 (Harness reading of the framework checklist, as for the other harnesses. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. The harness binds to loopback and keys stay in `~/.openmausbot`, but PostHog usage analytics are on until switched off, with a daily snapshot of what is set up, and the CLI guide says API keys are saved in plaintext with mode 0600 (18). Approval cards for provider permission requests, a narrow Always allow, isolated Local VMs and cloud computers, own-computer control off by default, and an MCP server that cannot approve, delete or touch credentials. New bots start at Full access, bot changes to skills, profiles and team setup apply without approval, and new bots keep every connected-app tool until grants are assigned (10). The docs say web page instructions never authorise credential use and that one-time codes go only to the site that sent them, and imported bots arrive with no grants, but bots read one-time codes from connected email without asking again (9). Per-thread NDJSON event logs, an Inspector, a decision log for connected-app grants and Undo lines for bot changes (12). SECURITY.md with an email, GitHub private vulnerability reporting enabled and scope notes that name one open risk. No published advisories, security.txt or bug bounty. npm releases use trusted publishing with provenance, and the Windows installer is unsigned (10).)