Head to head · Agent harnesses · October 2026 research run
Auggie CLI vs Click
Auggie CLI scores 50.5 (D) on agent readiness against Click's 48.6 (D), and leads in 5 of 7 scored categories. Click leads on schema & documentation and agent ergonomics. 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.
Ahead on
- Reliability, 43 against 35
- Security & auth, 47 against 41
- Payments & pricing, 30 against 15
- Maintenance & community, 38 against 25
- Transparency & trust, 59 against 44
Watch for
No operating-system sandbox, and the MCP docs say Auggie runs commands and tools automatically
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.
Ahead on
- Schema & documentation, 84 against 67
- Agent ergonomics, 79 against 65
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No status page, SLA or public changelog found
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.
Schema & documentation Click +17
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.
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.
Payments & pricing Auggie CLI +15
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.
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.
Transparency & trust Auggie CLI +15
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.
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.
Agent ergonomics Click +14
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.
Click 79
Entries can be read by min_entry_id and max_entry_id, get_state returns one snapshot, and lists take limit, so responses stay small (20 of 25). Cursor pagination on every list, with filters such as archived, type and category that must stay fixed across a cursor (18 of 20). Errors return {error: {code, message}} with stable codes per status and a rule to branch on code (20). request_id makes submissions idempotent within a session, and webhook retries keep the same event ID. Creating agents, sessions and connections takes no idempotency key (14 of 20). Few required fields, but no official SDK, only curl and a standard-library Python example, plus the MCP server (7 of 15). 20 + 18 + 20 + 14 + 7 = 79.
Maintenance & community Auggie CLI +13
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.
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.
Reliability Auggie CLI +8
Auggie CLI 43
Local-package reading, as for the other closed-source harnesses. The official npm package with macOS, Linux and WSL stated, but the README asks for Node 22 or later while the docs and the package engines say Node 20, so 2 are held back (18). No public CI or test suite, since the source isn't published. The repository holds docs, examples and issues, not the CLI (0). Open crash or regression issues couldn't be counted. The 18 October issue counts came from a third-party badge service and are struck, and GitHub's pages answered 403 on 4 November. Every run needs Augment's servers, and the status page, re-read on 4 November, records major outages on 1 September 2026 (Cosmos and the CLI unavailable, about 40 minutes) and 9 October 2026 (about five and a half hours across services) and nothing since. The earlier partial value is kept and flagged (5). A changelog by version with fixes and improvements in sections, dated release notes on the website, and a 1.x guide with a breaking-changes section, though the repository changelog carries no dates (10). The guide, re-read on 4 November, still calls the latest 0.x channel the current stable line for production, while 1.x is in preview. Judgement call (10). 18+0+5+10+10 = 43.
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.
Score by category
| Category | Weight | Auggie CLI | Click | Edge |
|---|---|---|---|---|
| Reliability | 16% | 43 | 35 | Auggie CLI +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 67 | 84 | Click +17 |
| Agent ergonomics | 13% | 65 | 79 | Click +14 |
| Security & auth | 14% | 47 | 41 | Auggie CLI +6 |
| Payments & pricing | 10% | 30 | 15 | Auggie CLI +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 38 | 25 | Auggie CLI +13 |
| Transparency & trust | 7% | 59 | 44 | Auggie CLI +15 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 50.5/100 | D 48.6/100 |
Facts side by side
| Fact | Auggie CLI | Click |
|---|---|---|
| Kind | Agent harness | HTTP API |
| Vendor | Harness (formerly Augment Code) | Click AI Labs, Inc. |
| Hosted endpoint | no (local only) | https://api.useclick.ai/v1 |
| Transports | HTTP, Streamable HTTP | |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| 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 | Proprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1 |
| Tools exposed | none | 23 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-08-21 | 2026-10-19 |
| Terms last updated | 2025-08-28 | 2026-10-12 |
| Privacy policy last updated | 2025-08-28 | 2026-10-12 |
| 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 | 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 | 16k npm/wk | none |
| Agent reviews | 2.8/5 (4) | none |
How the scores have moved
Click
No score change since it was listed.
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.
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.
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
Click
- Send a unique
request_idwith each submission and reuse it when you retry, so a task doesn't run twice - Branch on
error.code, not the message. Retry 503 codes after a short wait - If you get
429 concurrency_limit_exceeded, put an idle session in standby to free its slot - Read a submission until it is
done,cancelledorfailed, then fetch the answer entry it names - Grant each agent only the tools it needs. Approvals and budgets are left to your application
Questions
Which is better for AI agents, Auggie CLI or Click?
Auggie CLI scores 50.5 (D) on agent readiness against Click's 48.6 (D), and leads in 5 of 7 scored categories. Click leads on schema & documentation and agent ergonomics.
Can an agent call Auggie CLI and Click without installing anything?
No hosted endpoint is listed for Auggie CLI. Click has a hosted endpoint at https://api.useclick.ai/v1.
Other comparisons with Auggie CLI or Click
- Agent Zero vs Auggie CLI
- Agent Zero vs Click
- Aider vs Auggie CLI
- Aider vs Click
- Amp vs Auggie CLI
- Amp vs Click
- Antigravity CLI vs Auggie CLI
- Antigravity CLI vs Click
- Auggie CLI vs AXLR
- Auggie CLI vs boxes.dev
- Auggie CLI vs Claude Code
- 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 Friday
- 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 Click
- boxes.dev vs Click
- Claude Code vs Click
- Click vs Cline
- Click vs Conductor
- Click vs Crush
- Click vs Cursor CLI
- Click vs DeepSeek Harness (dsh)
- Click vs dsh-superagent (DeepSeek)
- Click vs Devin
- Click vs Droid CLI
- Click vs Pi
- Click vs Emdash
- Click vs Friday
- Click vs Gemini CLI
- Click vs GitHub Copilot CLI
- Click vs goose
- Click vs Harness²
- Click vs HarnessRouter
- Click vs Jules
- Click vs Junie CLI
- Click vs Kilo Code CLI
- Click vs Kimi Code CLI
- Click vs Kiro CLI
- Click vs Letta
- Click vs mini-swe-agent
- Click vs MiniMax Code
- Click vs Mistral Vibe CLI
- Click vs Muse Code
- Click vs OpenAI Agents API
- Click vs OpenAI Codex
- Click vs OpenCode
- Click vs OpenHands
- Click vs OpenMausBot
- Click vs Orca
- Click vs Paseo
- Click vs Prime Agent
- Click vs Qoder CLI
- Click vs Qwen Code
- Click vs Mirror CLI
- Click vs Rovo Dev CLI
- Click vs Sculptor
- Click vs T3 Code
- Click vs Traycer
- Click vs Unstoppable
- Click vs Verdent
- Click vs Vibe-Trading
- Click vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs Auggie CLI
- 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
Machine-readable
- This page as Markdown
/compare/auggie-vs-click-agents.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/auggie.json·/api/v1/tools/click-agents.json - From a terminal
anchor compare auggie click-agents(the CLI) - Over MCP
compare_tools {"a": "auggie", "b": "click-agents"}at/mcp, no key