Head to head · Agent harnesses · October 2026 research run

Click vs OpenMausBot

OpenMausBot scores 68.5 (B) on agent readiness against Click's 48.6 (D), and leads in 6 of 7 scored categories. Both do agent harnesses.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

Click D

Best for Product teams that want to embed an agent per customer, ticket or document without running the loop, sandbox or browser themselves, with any model.

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No status page, SLA or public changelog found

OpenMausBot B

Best 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 35
  • Schema & documentation, 90 against 84
  • Security & auth, 59 against 41
  • Payments & pricing, 75 against 15
  • Maintenance & community, 74 against 25
  • Transparency & trust, 59 against 44

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • Open source

Watch for

New bots start at Full access, which approves provider permission requests without a card

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing OpenMausBot +60

Click 15

No x402, MPP or L402. The only 402 is card_verification_required (0). Plan prices are public, Free at $0 and Pro at $199 a month with stated allowances, but no per-unit price (15). The Free plan exists, but writes return 402 until a card is verified in the dashboard (0). A person signs up in a browser, verifies a card and creates the key (0). 0 + 15 + 0 + 0 = 15.

OpenMausBot 75

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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Maintenance & community OpenMausBot +49

Click 25

Closed service with no dated changelog. The newest first-hand date is API version 2026-10-19, 30 days before this check, read as within 90 days rather than within 30 since nothing says what shipped then (20). No dated release entries to count (0). Support is by email to the founder, per the terms. No public changelog, issue tracker or community channel was found (5 of 15). No official SDK (0). No public package or CI to check (0). 20 + 0 + 5 + 0 + 0 = 25.

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.

Reliability OpenMausBot +25

Click 35

Hosted lines, for the HTTP API. No status page is linked from the site or the docs (0), so no incident history could be read (5). Concurrent session limits are published per plan (2 on Free, 50 on Pro) with body size limits of 16 MiB, but no request rate limits were found (8 of 15). 429 concurrency_limit_exceeded and the 503 codes are documented, the conventions say to retry 503 after a short wait, and request_id makes submissions safe to retry. No Retry-After header is documented (12 of 15). No SLA in the terms, which leave usage limits to Click's discretion (0). The API carries no beta or preview label (10). 0 + 5 + 8 + 12 + 0 + 10 = 35.

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).

Security & auth OpenMausBot +18

Click 41

Platform API keys are revocable, but each has full access to its tenant, including key management. The MCP server's OAuth tokens through WorkOS carry scopes for the MCP endpoint only (20 of 30). Tool grants limit each agent to named tools, and sessions can override grants, but approvals are left to the customer's application and no read-only key was found (8 of 20). Agents read web pages, browser content and MCP results. The docs tell users to keep secrets out of messages and keep MCP tools from returning stored secrets, but give no prompt-injection guidance (3 of 15). Every top-level and nested tool call is recorded and listed per session, and webhook deliveries can be listed (10 of 15). No security.txt (404), disclosure policy or certification found (0). 20 + 8 + 3 + 10 + 0 = 41.

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).

Transparency & trust OpenMausBot +15

Click 44

Closed service under terms based on the Common Paper Cloud Service Agreement 2.1, dated 12 October 2026, under Delaware law (15 of 30). The privacy statement lists what is collected, names PostHog with session replay for the website and dashboard, and says staff may access service content for support and to improve the service. Retention is "as long as reasonably needed" with no periods. The docs say Click-created sandboxes are deleted with their session (10 of 30). No deprecation policy. The terms promise 30 days' notice of price changes (3 of 20). Providers are described by category, with PostHog the only one named, and processing in the United States and other countries (5 of 20). 15 + 10 + 3 + 5 = 33.

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).

Schema & documentation OpenMausBot +6

Click 84

A public OpenAPI 3.2 document at useclick.ai/reference/openapi.yaml, API version 2026-10-19, rendered in full in llms-full.txt with 49 operations (25). llms.txt, llms-full.txt and a Markdown page per operation (10). The introduction says when to use Click, what Click runs and what the application owns, and each area explains its lifecycle (17 of 20). Typed schemas with 557 required-field markers in llms-full.txt and enumerated statuses, and string and body limits stated (12 of 15). A quick start with curl, a runnable Python example, and every operation lists its error codes by status (15). Paths are under /v1 with a dated API version, but no public changelog was found (5 of 15). 25 + 10 + 17 + 12 + 15 + 5 = 84.

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).

Score by category

CategoryWeightClickOpenMausBotEdge
Reliability16%3560OpenMausBot +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8490OpenMausBot +6
Agent ergonomics13%7977Click +2
Security & auth14%4159OpenMausBot +18
Payments & pricing10%1575OpenMausBot +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2574OpenMausBot +49
Transparency & trust7%4459OpenMausBot +15
Negative events≤150-2
TotalD 48.6/100B 68.5/100

Facts side by side

FactClickOpenMausBot
KindHTTP APIAgent harness
VendorClick AI Labs, Inc.Supamaus Software Private Limited
Hosted endpointhttps://api.useclick.ai/v1no (local only)
TransportsHTTP, Streamable HTTPstdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1Apache-2.0
Tools exposed2320
Read-only variant documentednono
llms.txtyesno
Last release2026-10-192026-11-01
Terms last updated2026-10-122026-10-10
Privacy policy last updated2026-10-122026-10-18
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone8.2k stars, 3.5k npm/wk

How the scores have moved

Click

No score change since it was listed.

OpenMausBot

Verdicts

Click

Click's API is described by a public OpenAPI 3.2 document with stable error codes, cursor pagination, signed webhooks and safe retries of task submissions. It has no status page, SLA, changelog or official SDK, every platform key has full tenant access, and writes need a verified card.

OpenMausBot

A bounded 20-tool MCP server with typed schemas, annotations and idempotent sends, and a headless CLI with JSON output and exit codes, let another agent hand work to a bot team and wait on it. New bots start at Full access, so provider permission requests pass without a card, and usage analytics stay on until switched off.

Before you call either

Click

  1. Send a unique request_id with each submission and reuse it when you retry, so a task doesn't run twice
  2. Branch on error.code, not the message. Retry 503 codes after a short wait
  3. If you get 429 concurrency_limit_exceeded, put an idle session in standby to free its slot
  4. Read a submission until it is done, cancelled or failed, then fetch the answer entry it names
  5. Grant each agent only the tools it needs. Approvals and budgets are left to your application

OpenMausBot

  1. Ask the owner for a pairing code from Settings > Phone, exchange it at POST /api/auth/pair, and set OPENMAUSBOT_TOKEN with an explicit OMB_PORT
  2. Pass a send_id with every send_bot_message and send_channel_message, so a retry returns the first receipt
  3. Use wait_for_conversation instead of polling, and on needs-user stop and tell the owner a card is waiting
  4. Check a bot's access level with the owner before sending work. New bots run at Full access unless defaults were changed
  5. Ask the owner to switch off Settings > General > Usage analytics if nothing beyond model calls should leave the machine

Questions

Which is better for AI agents, Click or OpenMausBot?

OpenMausBot scores 68.5 (B) on agent readiness against Click's 48.6 (D), and leads in 6 of 7 scored categories.

Can an agent call Click and OpenMausBot without installing anything?

Click has a hosted endpoint at https://api.useclick.ai/v1. OpenMausBot runs on your own machine, with no hosted endpoint listed.

Are Click and OpenMausBot open source?

No open-source release is listed for Click. OpenMausBot is open source (Apache-2.0).

Other comparisons with Click or OpenMausBot

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.