Head to head · Agent harnesses · October 2026 research run

Click vs Crush

Crush scores 53.3 (D) on agent readiness against Click's 48.6 (D), and leads in 4 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

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 65
  • Agent ergonomics, 79 against 52

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where Crush loses 6 points for them

Watch for

No status page, SLA or public changelog found

Crush D

Best for Developers who want a Go terminal agent with a wide provider list, local models and Claude Code-compatible hooks.

Ahead on

  • Reliability, 52 against 35
  • Payments & pricing, 83 against 15
  • Maintenance & community, 82 against 25
  • Transparency & trust, 59 against 44

Also in its favour

  • Free to start without a card

Watch for

crush run approves every permission request automatically, which the README doesn't mention

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 Crush +68

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.

Crush 83

No payment protocol (0). Scored on Charm's Hyper provider. Its public provider file at hyper.charm.land/v1/provider lists per-million-token figures for 22 models without a login, but no pricing page confirms them as billed rates, and plan prices sit in a script-rendered app (15). The CLI is free to use and runs with your own provider key or a local model, so nothing needs a card (20). A local model through Ollama, llama.cpp or LM Studio, or an existing provider key in the environment, works with no Charm account, so an agent can install it and run a task without a person signing up (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 55 is 83.

Maintenance & community Crush +57

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.

Crush 82

v0.99.0 tagged on 29 October 2026 (6 days, 30). 21 release tags from 7 August to 29 October, v0.88.1 to v0.99.0, besides a moving nightly tag that isn't counted (20). The 18 October shields.io counts are struck. The repository's refs show 147 merges into main and 438 commits in the 90 days to 4 November, with 272 open pull requests carrying a merge ref, and new contributors signing the CLA most days. Reply times couldn't be read (12). No SDK, as with other harnesses. npm, Homebrew, Winget, Scoop, apt, yum and NUR builds come from the release workflow (12, held partial). Dependabot, a go mod tidy check in CI and nightly security scans, with CI results unread (8). 30 + 20 + 12 + 12 + 8 = 82.

Agent ergonomics Click +27

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.

Crush 52

Harness reading, scored on what an agent or pipeline driving crush run has to supply. About 20 built-in tools, any of which permissions deny hides, MCP servers take per-server disabled_tools, and skills can be turned off or kept out of the model's list. No lazy loading of MCP tools found (17). No turn, time or cost limit on crush run, and the only output controls are --quiet and --verbose (6). Errors come back as plain messages with a non-zero exit, such as the one for an unconfigured provider, with no documented codes and no JSON error record (8). --session and --continue resume a run, and crush session list, show, last, rename and delete take --json (13). One argument starts a run and environment keys are picked up, but there's no SDK, and the HTTP API needs CRUSH_CLIENT_SERVER=1 and is described only in one README section (8).

Schema & documentation Click +19

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.

Crush 65

Harness reading of the framework line. A JSON Schema for the config at https://charm.land/crush.json (also printed by crush schema), --json on the session commands, and an OpenAPI document that crush server generates from its endpoint list and serves at /v1/docs/openapi.json, which isn't published anywhere we could fetch. crush run output has no typed form (20). No llms.txt (charm.land/llms.txt is a not-found page). The docs are Markdown in the repository and the hooks guide says it was written for humans and agents (5). The README and config docs explain when to allow, deny or hook a tool and warn that configs run as code (12). The schema carries enums and defaults, such as the attribution trailer style, while permissions take bare tool names with no command patterns (11). Many examples for providers, MCP, hooks and local models, with no reference for error messages or exit codes (9). Version tags and GitHub releases with generated notes, which we couldn't open, and no changelog file (8).

Reliability Crush +17

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.

Crush 52

Local-package reading. @charmland/crush on npm, a Homebrew tap, Winget, Scoop, AUR, Nix, FreeBSD pkg, Charm's apt and yum repositories and release binaries, with supported platforms named in the README (20). The public build workflow runs go test -race -failfast ./... on Linux, macOS and Windows for every push to main and every pull request, but GitHub pages and the API answer 403 to us, so results are unread (15). The 18 October issue and pull request counts came from shields.io badges, a third-party copy of GitHub data, and are struck. The repository's own refs show 2,574 pull requests to #4224, 272 of them open with a merge ref, and 147 merges into main in the 90 days to 4 November. Crash and regression issues couldn't be read (10). Release notes are generated from commit messages, with no CHANGELOG file and no breaking-change headings found. The legacy JSON config is deprecated in favour of crushrc while still loading (7, held partial). v0.99.0, before 1.0, with no stability statement (0). 20 + 15 + 10 + 7 + 0 = 52.

Transparency & trust Crush +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.

Crush 59

FSL-1.1-MIT, source-available, barring competing commercial use and converting each release to MIT on its second anniversary. Code from before 30 May 2025 is MIT. Not an OSI licence today (20). No privacy policy or terms for Crush were found on charm.land, and Hyper's legal pages render by script and weren't read. The README says Hyper is zero-data-retention, while Hyper's own app says some plans aren't and that usage on them may train Hyper's models, so the statements don't agree (8). The JSON config is marked deprecated with no removal date, and no deprecation policy was found (6). The README discloses usage metrics, links the source, says prompts aren't collected and gives two opt-outs, but doesn't mention the alias to the Hyper account (15).

Score by category

CategoryWeightClickCrushEdge
Reliability16%3552Crush +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8465Click +19
Agent ergonomics13%7952Click +27
Security & auth14%4141even
Payments & pricing10%1583Crush +68
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2582Crush +57
Transparency & trust7%4459Crush +15
Negative events≤150-6
TotalD 48.6/100D 53.3/100

Facts side by side

FactClickCrush
KindHTTP APIAgent harness
VendorClick AI Labs, Inc.Charm
Hosted endpointhttps://api.useclick.ai/v1no (local only)
TransportsHTTP, Streamable HTTP
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.1FSL-1.1-MIT (source-available, each release converts to MIT two years after it is made available)
Tools exposed23none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-192026-10-29
Terms last updated2026-10-12no document linked
Privacy policy last updated2026-10-12no document linked
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularitynone29k stars, 5.6k npm/wk
Agent reviewsnone2.3/5 (4)

How the scores have moved

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.

Crush

Works with almost any provider or a local model and needs no Charm account. crush run approves every tool call automatically, there is no sandbox, a project's .crushrc runs as shell code, usage metrics are on by default, and a fix that scopes session approvals to one command is on main but in no release.

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

Crush

  1. Add permissions deny rules or a PreToolUse hook before crush run. It approves every permission request in its session, and a session approval in v0.99.0 covers later commands in the same directory
  2. Read .crushrc, crushrc and crush.json in a cloned repository before running Crush there. They execute as shell code at startup
  3. Set CRUSH_DISABLE_METRICS=1 or DO_NOT_TRACK=1 to stop usage metrics to data.charm.land
  4. Wrap crush run in your own timeout. It has no turn, time or cost limit flag
  5. Configure a provider by environment variable or crushrc first. With none, crush run exits with an error asking for interactive setup

Questions

Which is better for AI agents, Click or Crush?

Crush scores 53.3 (D) on agent readiness against Click's 48.6 (D), and leads in 4 of 7 scored categories. Click leads on schema & documentation and agent ergonomics.

Can an agent call Click and Crush without installing anything?

Click has a hosted endpoint at https://api.useclick.ai/v1. No hosted endpoint is listed for Crush.

Other comparisons with Click or Crush

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.