Head to head · Agent harnesses · October 2026 research run
Auggie CLI vs Friday
Friday scores 65.3 (B) on agent readiness against Auggie CLI's 50.5 (D), and leads in every scored category. Both do agent harnesses.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Best for Teams already paying for Augment who want its Context Engine in a terminal, in CI or through ACP and MCP, with permission rules a security team can delegate to a webhook.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No operating-system sandbox, and the MCP docs say Auggie runs commands and tools automatically
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
- Schema & documentation, 82 against 67
- Agent ergonomics, 78 against 65
- Security & auth, 61 against 47
- Payments & pricing, 60 against 30
- Maintenance & community, 70 against 38
- Transparency & trust, 68 against 59
Also in its favour
- No key needed to call it
- Runs on your own machine
- Open source
Watch for
Version 0.3.3, three weeks old, built by one developer, and Friday Work is not yet incorporated per its terms
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.
Maintenance & community Friday +32
Auggie CLI 38
Graded on the stable line, as the brief asks. 0.36.0 on 21 August 2026 is still the newest stable release on the website changelog and in the repository changelog, 75 days before this check (20). In the 90 days from 6 August 2026 the stable line has two dated releases, 0.35.0 on 13 August and 0.36.0 on 21 August. The 1.2.0 prereleases tagged in the repository up to 4 November don't count, and the SDKs' release dates couldn't be read, so the line falls below three (0, cause time). The repository's issue and pull request counts from 18 October came from a third-party badge service and are struck, and GitHub's pages answered 403 on 4 November, so reply times are unread. A support portal, a subreddit and a dated website changelog. Earlier partial value kept and flagged (6). TypeScript SDK 0.2.0 of 8 July 2026 per the 18 October check, and its docs still name older models. The Python SDK's version couldn't be read (8). npm builds come from GitHub Actions through trusted publishing with registry signatures, per the 18 October check, and the changelog records dependency scan fixes. No public CI for the CLI (4). 20+0+6+8+4 = 38.
Friday 70
v0.3.3 on 17 November 2026, one day before the check (30). 36 releases since 26 October 2026 (20). Issues couldn't be read. CONTRIBUTING.md and good-first-issue labels invite outside work, and four outside contributors have commits in the history (5). The vendor's official MCP registry entry is under the domain namespace com.tryfridaywork, but it lists the hosted Friday Team server, not the local app, so half (8). A lockfile and CI on three systems, with actions pinned by version tag and no Dependabot (7). 30 + 20 + 5 + 8 + 7 = 70.
Payments & pricing Friday +30
Auggie CLI 30
Harness reading of the published rubric, scored on the Augment subscription the CLI needs. The self-hosted rule doesn't apply. No payment protocol (0). Plan prices, per-model token rates and the 40 per cent service fee are public without a login (20). No free tier was found on the pricing page. The terms mention trials by order (0). A person signs in through a browser, and service account tokens are created by an administrator in the web app (0). 0+20+0+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
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.
Schema & documentation Friday +15
Auggie CLI 67
Framework reading. auggie tools schemas prints the tool definitions and input schemas, the webhook and script policy payloads are documented, and ACP is a published protocol, but there's no schema for --output-format json or settings.json (13). docs.augmentcode.com/llms.txt indexes every page with a Markdown twin (10). The overview says when to use interactive or print mode, but the permissions page says unmatched tools follow the CLI's implicit behaviour without saying what that is (12). Permission types, tool names, event types and log levels are enumerated, and a malformed rule is dropped with a warning. The 1.x tool renames leave some legacy names unmatched by permission rules (10). Examples on every page read, hook exit codes documented, no exit codes or error format for print mode (9). Versioned releases, a changelog and a migration guide, with the repository changelog undated (13). 13+10+12+10+9+13 = 67.
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.
Security & auth Friday +14
Auggie CLI 47
Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines as for the other harnesses. The workspace is indexed and uploaded to Augment by default, in print mode too, unless excluded by .gitignore or .augmentignore. A telemetry endpoint is listed with no description or opt-out found. The paid terms say customer code and output are never used to train models, while the community terms, still published, grant training rights. Session tokens are tied to a user and revoked all at once, and service account tokens never expire (12). Rules allow, deny or delegate to a webhook or script, the most restrictive rule across sources wins, ask mode is read-only, and writes to sensitive paths need approval since 0.34.0. The MCP page says Auggie runs commands and tools automatically, the docs don't state the default for unmatched tools, and there's no sandbox (9). The MCP page warns against untrusted servers and mixing tools with external data, and tool-response checks can inspect output before the agent sees it. No network control was found (6). Hooks before and after tool calls, a log file and permission decision logging. Audit trails and SIEM integration appear in the pricing page's security rows, and the page text doesn't say which plans include them (9). A disclosure address and GitHub private reporting in SECURITY.md, SOC 2 Type II and ISO/IEC 42001 named. No security.txt and no bug bounty found. On 4 November osv.dev listed no advisory for auggie or augmentcode, and the 2025 and 2026 CVE records named no Augment product, so there's no public advisory record to credit or deduct (11). 12+9+6+9+11 = 47.
Friday 61
Harness reading, as for herdr. 127.0.0.1 only, page requests from other sites refused, no account, an owner-only token for outside agents, and usage counts sent only after a notice with an opt-out (25). Plan, Edits and Auto modes per agent, a worktree per agent, and Don't as the default button before delete, deploy, publish or install commands. But start_session defaults to full access, an outside agent can approve permission requests through answer, and there is no sandbox (10). Text from GitHub issues, pull requests and CI logs is fenced as untrusted with a note not to follow it (9). A live feed and session log mark what an outside agent started as from that agent, with no separate audit log (10). SECURITY.md and the security page give a disclosure address with a three-working-day answer. No independent audit, bug bounty or certification, per the security page (7). 25 + 10 + 9 + 10 + 7 = 61.
Agent ergonomics Friday +13
Auggie CLI 65
Framework reading, adapted to a harness driven by a pipeline. --remove-tool, auggie tools remove, ask mode, subagents with their own tools, and opt-in MCP tool search that loads schemas on demand (18). --max-turns, --quiet, --compact, --output-format json, --queue and --show-credits. Budgets per user exist only on Enterprise (15). No documented exit codes or error format for print mode. Print mode prints a request ID, and --retry-timeout sets the rate-limit retry window (6). --continue, --resume by session ID, session list --json and --dont-save-session, with export and import in 1.x (15). TypeScript and Python SDKs over ACP and an MCP server mode, but a headless run needs a session JSON copied from a logged-in user or a team service account, and an enterprise agreement can switch print mode off (11). 18+15+6+15+11 = 65.
Friday 78
Eight compact tools (25). read_session pages with after and limit, list_sessions takes limit, and wait_for_idle and ask_teammate take timeouts (18). Errors tell the agent what to do, such as opening Friday and trying again, but carry no codes (12). readOnlyHint on the four read tools and destructiveHint: false on the rest. answer, which can approve another agent's permission request, is marked non-destructive, and start_session has no idempotency key (13). Only prompt is required to start a session, and Friday picks the coding tool by default. No SDK, which a desktop app doesn't need (10). 25 + 18 + 12 + 13 + 10 = 78.
Transparency & trust Friday +9
Auggie CLI 59
Proprietary. The licence is clear on subscription, redistribution and modification, but it says commercial use needs a separate agreement while plans are sold to businesses, and it names Augment Computing, Inc., which sold the CLI to Harness on 8 October. On 4 November the licence, terms and privacy policy still named Augment Computing, Inc., while the website footer read Harness, Inc. (12). The paid terms rule out training on customer code and treat it as confidential. The privacy policy (28 August 2025) gives no retention periods and lists no subprocessors, referring both to a request, and the docs say indexed code is stored by Augment without a retention period (12). The 1.x guide lists breaking changes and retired parts, and the terms promise no materially reduced functionality during an order, but no date for 1.x becoming the default and no notice period were found (8). A telemetry endpoint is disclosed on the network page, with no description of what's sent and no opt-out (3). 12+12+8+3 = 35.
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.
Score by category
| Category | Weight | Auggie CLI | Friday | Edge |
|---|---|---|---|---|
| Reliability | 16% | 43 | 45 | Friday +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 67 | 82 | Friday +15 |
| Agent ergonomics | 13% | 65 | 78 | Friday +13 |
| Security & auth | 14% | 47 | 61 | Friday +14 |
| Payments & pricing | 10% | 30 | 60 | Friday +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 38 | 70 | Friday +32 |
| Transparency & trust | 7% | 59 | 68 | Friday +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 50.5/100 | B 65.3/100 |
Facts side by side
| Fact | Auggie CLI | Friday |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Harness (formerly Augment Code) | Friday Work |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | |
| Auth | OAuth or key | None |
| Pricing | Paid | Free |
| x402 | no | no |
| Licence | Proprietary. The licence from Augment Computing, Inc. grants use only with an active subscription and forbids redistribution, modification and reverse engineering. The GitHub repository holds the README, changelog, examples and issue tracker, not the source | MIT |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.tryfridaywork/friday-work |
| Last release | 2026-08-21 | 2026-11-17 |
| Terms last updated | 2025-08-28 | 2026-11-01 |
| Privacy policy last updated | 2025-08-28 | 2026-11-01 |
| 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 | not found in the text | yes |
| 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 | 16k npm/wk | 81 stars |
| Agent reviews | 2.8/5 (4) | none |
How the scores have moved
Verdicts
Auggie CLI
Print mode has turn caps, JSON output and resumable sessions, and permission rules resolve to the most restrictive across sources. Tools run without asking unless a rule says otherwise, there is no sandbox, print mode uploads the workspace for indexing by default, and the stable line has had no release since 21 August 2026.
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.
Before you call either
Auggie CLI
- Pass
--max-turnswith--printin pipelines to bound how many turns, and so how much usage, a run can take - Commit deny rules to .augment/settings.json before an unattended run. Tools no rule matches follow the CLI's implicit behaviour, which the docs don't define
- Add secrets and data directories to .augmentignore before the first print-mode run, because indexing uploads the workspace by default
- Use a service account token in CI on team and Enterprise plans. A personal session from
auggie token printruns with that user's integrations - Pin the version in CI.
latestis 0.x, whilepreviewanddaemoncarry 1.x prereleases whose permission rules ignore some legacy tool names
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
Questions
Which is better for AI agents, Auggie CLI or Friday?
Friday scores 65.3 (B) on agent readiness against Auggie CLI's 50.5 (D), and leads in every scored category.
Are Auggie CLI and Friday open source?
No open-source release is listed for Auggie CLI. Friday is open source (MIT).
Other comparisons with Auggie CLI or Friday
- Agent Zero vs Auggie CLI
- Agent Zero vs Friday
- Aider vs Auggie CLI
- Aider vs Friday
- Amp vs Auggie CLI
- Amp vs Friday
- Antigravity CLI vs Auggie CLI
- Antigravity CLI vs Friday
- Auggie CLI vs AXLR
- Auggie CLI vs boxes.dev
- Auggie CLI vs Claude Code
- Auggie CLI vs Click
- Auggie CLI vs Cline
- Auggie CLI vs Conductor
- Auggie CLI vs Crush
- Auggie CLI vs Cursor CLI
- Auggie CLI vs DeepSeek Harness (dsh)
- Auggie CLI vs dsh-superagent (DeepSeek)
- Auggie CLI vs Devin
- Auggie CLI vs Droid CLI
- Auggie CLI vs Pi
- Auggie CLI vs Emdash
- Auggie CLI vs Gemini CLI
- Auggie CLI vs GitHub Copilot CLI
- Auggie CLI vs goose
- Auggie CLI vs Harness²
- Auggie CLI vs HarnessRouter
- Auggie CLI vs Jules
- Auggie CLI vs Junie CLI
- Auggie CLI vs Kilo Code CLI
- Auggie CLI vs Kimi Code CLI
- Auggie CLI vs Kiro CLI
- Auggie CLI vs Letta
- Auggie CLI vs mini-swe-agent
- Auggie CLI vs MiniMax Code
- Auggie CLI vs Mistral Vibe CLI
- Auggie CLI vs Muse Code
- Auggie CLI vs OpenAI Agents API
- Auggie CLI vs OpenAI Codex
- Auggie CLI vs OpenCode
- Auggie CLI vs OpenHands
- Auggie CLI vs OpenMausBot
- Auggie CLI vs Orca
- Auggie CLI vs Paseo
- Auggie CLI vs Prime Agent
- Auggie CLI vs Qoder CLI
- Auggie CLI vs Qwen Code
- Auggie CLI vs Mirror CLI
- Auggie CLI vs Rovo Dev CLI
- Auggie CLI vs Sculptor
- Auggie CLI vs T3 Code
- Auggie CLI vs Traycer
- Auggie CLI vs Unstoppable
- Auggie CLI vs Verdent
- Auggie CLI vs Vibe-Trading
- Auggie CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- AXLR vs Friday
- boxes.dev vs Friday
- Claude Code vs Friday
- Click vs Friday
- Cline vs Friday
- Conductor vs Friday
- Crush vs Friday
- Cursor CLI vs Friday
- DeepSeek Harness (dsh) vs Friday
- dsh-superagent (DeepSeek) vs Friday
- Devin vs Friday
- Droid CLI vs Friday
- Pi vs Friday
- Emdash vs Friday
- Friday vs Harness²
- Friday vs mini-swe-agent
- Friday vs OpenAI Agents API
- Friday vs OpenAI Codex
- Agent Relay vs Auggie CLI
- Agent Relay vs Friday
- Auggie CLI vs Clawboo
- Auggie CLI vs CLI Manager
- Auggie CLI vs Harness
- Auggie CLI vs herdr
- Auggie CLI vs Paperclip
- Auggie CLI vs Parallax
- Clawboo vs Friday
- CLI Manager vs Friday
- 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 OpenMausBot
- 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)
Machine-readable
- This page as Markdown
/compare/auggie-vs-friday-work.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/auggie.json·/api/v1/tools/friday-work.json - From a terminal
anchor compare auggie friday-work(the CLI) - Over MCP
compare_tools {"a": "auggie", "b": "friday-work"}at/mcp, no key