Head to head · Multi-agent orchestration · October 2026 research run
Friday vs OpenMausBot
OpenMausBot scores 68.5 (B) on agent readiness against Friday's 65.3 (B), and leads in 4 of 7 scored categories. Friday leads on transparency & trust. Both do multi-agent orchestration.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Friday B
Best for A person who already runs several coding CLIs and wants an outside agent to hand work to them and wait on the result.
Ahead on
- Transparency & trust, 68 against 59
Also in its favour
- No key needed to call it
Watch for
Version 0.3.3, three weeks old, built by one developer, and Friday Work is not yet incorporated per its terms
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 45
- Schema & documentation, 90 against 82
- Payments & pricing, 75 against 60
Also in its favour
- Free to start without a card
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.
Reliability OpenMausBot +15
Friday 45
Read as local software, as for herdr and Orca. Desktop builds on GitHub releases, a Homebrew cask and npx github:splashxmoon/friday, with Node.js 22 stated (20). .github/workflows/ci.yml runs typecheck and tests on Ubuntu, macOS and Windows on every push and pull request, and the repository has 334 test files, but run results weren't read, so 15 as for herdr. Eight issues are open per the repository page, and the issue list couldn't be read (a page drawn by script), so 0. Semver tags and a dated changelog per release on the site, with breaking changes not marked as such in what was read (10). Version 0.3.3, not 1.0 (0). 20 + 15 + 0 + 10 + 0 = 45.
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).
Payments & pricing OpenMausBot +15
Friday 60
Scored on the hosted option, as for Orca. No payment protocol (0). Friday Team is priced on request, with no price on the pages read (0). The app is free and MIT licensed with no card (30). The app needs no account or sign-up (30). 0 + 0 + 30 + 30 = 60.
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.
Transparency & trust Friday +9
Friday 68
MIT (30). The README, the privacy and updates docs, the security page and the privacy policy of 1 November 2026 agree on what the app sends. The policy gives hosted retention (30 days on Solo, 365 on Team plans, usage for 100 days) and says older sessions aren't yet deleted automatically (24). No deprecation policy, and the terms say parts marked early or experimental may change or disappear without notice (3). Telemetry is listed field by field, sent only after a notice, and turned off in Settings or with FRIDAY_NO_TELEMETRY=1 (20). 30 + 24 + 3 + 20 = 77.
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 +8
Friday 82
Read on the outside-agent MCP server. Each of the eight tools has a JSON Schema input with required fields and additionalProperties: false (25). llms.txt, llms-full.txt and every page as Markdown with Accept: text/markdown (10). Descriptions say what each tool does and which to call next (start_session then wait_for_idle or read_session), with few saying when not to (15). Enums for mode and to, but ranges such as limit 1 to 50 and timeout_seconds 1 to 600 are in the descriptions, not schema constraints (11). Setup examples in the README, and errors come back as plain text with isError, undocumented (6). Semver tags and a dated public changelog (15). 25 + 10 + 15 + 11 + 6 + 15 = 82.
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
| Category | Weight | Friday | OpenMausBot | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 60 | OpenMausBot +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 90 | OpenMausBot +8 |
| Agent ergonomics | 13% | 78 | 77 | Friday +1 |
| Security & auth | 14% | 61 | 59 | Friday +2 |
| Payments & pricing | 10% | 60 | 75 | OpenMausBot +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 74 | OpenMausBot +4 |
| Transparency & trust | 7% | 68 | 59 | Friday +9 |
| Negative events | ≤15 | 0 | -2 | |
| Total | B 65.3/100 | B 68.5/100 |
Facts side by side
| Fact | Friday | OpenMausBot |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Friday Work | Supamaus Software Private Limited |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | stdio |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT | Apache-2.0 |
| Tools exposed | 8 | 20 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | com.tryfridaywork/friday-work | not listed |
| Last release | 2026-11-17 | 2026-11-01 |
| Terms last updated | 2026-11-01 | 2026-10-10 |
| Privacy policy last updated | 2026-11-01 | 2026-10-18 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 81 stars | 8.2k stars, 3.5k npm/wk |
How the scores have moved
Verdicts
Friday
Outside agents can hand work to Friday through eight compact MCP tools with typed inputs and read-only hints, and the app sends usage counts only after asking. It is a three-week-old 0.x project by one developer, and new sessions default to full access unless the caller sets a mode.
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
Friday
- Set
modetoplanoreditsinstart_sessionunless the person asked for full access. The default isfull - Leave
answerwithapprove: trueto the person unless they told you to approve requests for them - If
wait_for_idletimes out, call it again rather than starting a new session - If a call says Friday isn't running, ask the person to open Friday, then retry
- Page
read_sessionwithafterset to the lastnext_afterinstead of reading the whole history each time
OpenMausBot
- Ask the owner for a pairing code from Settings > Phone, exchange it at
POST /api/auth/pair, and setOPENMAUSBOT_TOKENwith an explicitOMB_PORT - Pass a
send_idwith everysend_bot_messageandsend_channel_message, so a retry returns the first receipt - Use
wait_for_conversationinstead of polling, and onneeds-userstop and tell the owner a card is waiting - Check a bot's access level with the owner before sending work. New bots run at Full access unless defaults were changed
- 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, Friday or OpenMausBot?
OpenMausBot scores 68.5 (B) on agent readiness against Friday's 65.3 (B), and leads in 4 of 7 scored categories. Friday leads on transparency & trust.
Are Friday and OpenMausBot open source?
Yes. Friday is open source (MIT). OpenMausBot is open source (Apache-2.0).
Other comparisons with Friday or OpenMausBot
- Agent Zero vs Friday
- Agent Zero vs OpenMausBot
- Aider vs Friday
- Aider vs OpenMausBot
- Amp vs Friday
- Amp vs OpenMausBot
- Antigravity CLI vs Friday
- Antigravity CLI vs OpenMausBot
- Auggie CLI vs Friday
- Auggie CLI vs OpenMausBot
- AXLR vs Friday
- AXLR vs OpenMausBot
- boxes.dev vs Friday
- boxes.dev vs OpenMausBot
- Claude Code vs Friday
- Claude Code vs OpenMausBot
- Click vs Friday
- Click vs OpenMausBot
- Cline vs Friday
- Cline vs OpenMausBot
- Conductor vs Friday
- Conductor vs OpenMausBot
- Crush vs Friday
- Crush vs OpenMausBot
- Cursor CLI vs Friday
- Cursor CLI vs OpenMausBot
- DeepSeek Harness (dsh) vs Friday
- DeepSeek Harness (dsh) vs OpenMausBot
- dsh-superagent (DeepSeek) vs Friday
- dsh-superagent (DeepSeek) vs OpenMausBot
- Devin vs Friday
- Devin vs OpenMausBot
- Droid CLI vs Friday
- Droid CLI vs OpenMausBot
- Pi vs Friday
- Pi vs OpenMausBot
- Emdash vs Friday
- Emdash vs OpenMausBot
- Friday vs Harness²
- Friday vs mini-swe-agent
- Friday vs OpenAI Agents API
- Friday vs OpenAI Codex
- Gemini CLI vs OpenMausBot
- GitHub Copilot CLI vs OpenMausBot
- goose vs OpenMausBot
- Harness² vs OpenMausBot
- HarnessRouter vs OpenMausBot
- Jules vs OpenMausBot
- Junie CLI vs OpenMausBot
- Kilo Code CLI vs OpenMausBot
- Kimi Code CLI vs OpenMausBot
- Kiro CLI vs OpenMausBot
- Letta vs OpenMausBot
- mini-swe-agent vs OpenMausBot
- MiniMax Code vs OpenMausBot
- Mistral Vibe CLI vs OpenMausBot
- Muse Code vs OpenMausBot
- OpenAI Agents API vs OpenMausBot
- OpenAI Codex vs OpenMausBot
- OpenCode vs OpenMausBot
- OpenHands vs OpenMausBot
- Agent Relay vs Friday
- Agent Relay vs OpenMausBot
- Clawboo vs Friday
- Clawboo vs OpenMausBot
- CLI Manager vs Friday
- CLI Manager vs OpenMausBot
- Friday vs Gemini CLI
- Friday vs GitHub Copilot CLI
- Friday vs goose
- Friday vs Harness
- Friday vs HarnessRouter
- Friday vs herdr
- Friday vs Jules
- Friday vs Junie CLI
- Friday vs Kilo Code CLI
- Friday vs Kimi Code CLI
- Friday vs Kiro CLI
- Friday vs Letta
- Friday vs MiniMax Code
- Friday vs Mistral Vibe CLI
- Friday vs Muse Code
- Friday vs OpenCode
- Friday vs OpenHands
- Friday vs Orca
- Friday vs Paperclip
- Friday vs Parallax
- Friday vs Paseo
- Friday vs Prime Agent
- Friday vs Qoder CLI
- Friday vs Qwen Code
- Friday vs Mirror CLI
- Friday vs Rovo Dev CLI
- Friday vs Sculptor
- Friday vs T3 Code
- Friday vs Traycer
- Friday vs Unstoppable
- Friday vs Verdent
- Friday vs Vibe-Trading
- Friday vs Warp (Warp Agent CLI and the Oz Agent API)
- Harness vs OpenMausBot
- herdr vs OpenMausBot
- OpenMausBot vs Orca
- OpenMausBot vs Paperclip
- OpenMausBot vs Parallax
- OpenMausBot vs Paseo
- OpenMausBot vs Prime Agent
- OpenMausBot vs Qoder CLI
- OpenMausBot vs Qwen Code
- OpenMausBot vs Mirror CLI
- OpenMausBot vs Rovo Dev CLI
- OpenMausBot vs Sculptor
- OpenMausBot vs T3 Code
- OpenMausBot vs Traycer
- OpenMausBot vs Unstoppable
- OpenMausBot vs Verdent
- OpenMausBot vs Vibe-Trading
- OpenMausBot vs Warp (Warp Agent CLI and the Oz Agent API)
Machine-readable
- This page as Markdown
/compare/friday-work-vs-openmausbot.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/friday-work.json·/api/v1/tools/openmausbot.json - From a terminal
anchor compare friday-work openmausbot(the CLI) - Over MCP
compare_tools {"a": "friday-work", "b": "openmausbot"}at/mcp, no key