Head to head · Agent harnesses · October 2026 research run
Click vs Droid CLI
Droid CLI scores 57.8 (C) 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 79
- Agent ergonomics, 79 against 72
Also in its favour
- A hosted endpoint, with nothing to install
- No incidents deducted, where Droid CLI loses 3 points for them
Watch for
No status page, SLA or public changelog found
Best for Teams that want a terminal coding agent with tiered autonomy, command rules and an optional sandbox, and that will pay for a Factory plan.
Ahead on
- Reliability, 54 against 35
- Security & auth, 63 against 41
- Maintenance & community, 79 against 25
- Transparency & trust, 65 against 44
Watch for
No free tier or trial was found. Plans start at $20 a month and included usage is stated only as rolling rate limits without numbers
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 Droid CLI +54
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.
Droid CLI 79
The changelog's newest entry is CLI v1.3.0 of 4 November 2026 (30). 67 dated changelog entries between 6 August and 4 November 2026, 20 of them after 9 October (20). The public tracker had 33 open issues that are not pull requests on 9 October 2026, most with no reply, and three closed in the previous week after two or three comments, not re-read on 4 November. Support is also by email and Discord, where reply times are not visible (9). The TypeScript SDK repository moved to 0.10.0 with examples tested in CI on 20 October 2026, and the Python SDK is at 0.5.0 of 24 September 2026 (15). The npm package is published from GitHub Actions through a trusted publisher and the installer checks a checksum, per the 9 October check. There is no public CI for the CLI (5).
Security & auth Droid CLI +22
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.
Droid CLI 63
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 agent loop runs locally and the docs say no copy of the repository is uploaded or indexed. Prompts and context go to the model endpoints. Usage metrics go to Factory's collector by default, with no opt-out in the pages read outside an airgapped deployment, and message content is never sent to it. The security page says code is not used as training data. Zero data retention is listed as a Business plan item. Headless runs use a long-lived fk- key (17). droid exec is read-only by default, autonomy has four levels, permission rules allow, ask or block commands, and an OS sandbox confines commands with Seatbelt or bubblewrap and a network proxy. The sandbox is off by default and --skip-permissions-unsafe skips every prompt (16). The sandbox page names prompt injection and states what the sandbox does not stop, MCP approvals are bound to the server's command or URL, and Droid Shield scans commits for secrets. The Agent Safety page was not read (9). An organisation audit log, OpenTelemetry export and session tags exist, with audit logging listed from the Business plan up (10). A disclosure address (security@factory.com), SOC 2 and ISO 42001 named on the security page, per the 9 October check, and Security sections in the changelog. No security.txt (404 on 4 November), no bug bounty and no published advisories were found, OSV holds nothing for droid, and the trust centre was not readable (11).
Transparency & trust Droid CLI +21
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.
Droid CLI 65
Closed source under terms from The San Francisco AI Factory, Inc., last updated 14 July 2026. The npm package is marked UNLICENSED and the Python SDK is Apache-2.0 (15). The Data Flows page says where code, prompts and telemetry go in each deployment pattern, and the privacy policy (20 August 2026) lists service providers with the place of processing and keeps personal data up to 10 years after last use. Retention of Factory's operational logs is left to the trust centre, which we could not read, and whether session transcripts are stored in Factory's cloud on individual plans was not established (17). The terms promise commercially reasonable efforts to give 60 days' notice of major changes, the changelog has Deprecations sections, and the old command lists are deprecated but still honoured. A model retirement appeared in the changelog on the day it took effect, 11 August 2026 (12). The telemetry reference documents each metric and what reaches Factory, and telemetry.granularity can strip user identity. Metrics to Factory are on by default, with no opt-out found outside an airgapped deployment (11).
Reliability Droid CLI +19
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.
Droid CLI 54
Local-package reading, as for the other closed-source harnesses. An install script that verifies a SHA-256 checksum, a PowerShell installer, a Homebrew cask and the droid npm package (Node 20 or later) with prebuilt binaries for Linux, macOS and Windows on x64 and arm64, per the 9 October check (20). The source is not published. The public repository holds documentation only, so there is no public CI or test suite for the CLI (0). Bugs are tracked in the open at Factory-AI/factory. On 9 October 2026 it had 33 open issues that are not pull requests, most with no reply, and three closed in the previous week with replies. Issues were not re-read on 4 November because GitHub's API refused our requests (10). Every release has a dated, versioned changelog entry and deprecations get their own section. The line moved from 0.251.0 to 1.0.0 on 29 October, with three minors since, so the version number has signalled breaking changes for only six days (9). CLI v1.0.0 was released on 29 October 2026 and v1.3.0 on 4 November (15). The 99 per cent availability target on factory.com/sla is not scored on this reading.
Agent ergonomics Click +7
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.
Droid CLI 72
Harness reading of the framework line. --restrict-tools, --disabled-tools, --additional-tools and --list-tools control built-in tools per run, and disabledTools in mcp.json keeps named MCP tools out of context. We found nothing on deferred tool loading (18). Output is text, json, stream-json or stream-jsonrpc, and the JSON result carries turns and duration. The droid exec help lists no flag for a turn or spend limit (10). Exit codes 0, 1 and 2 are documented, and a run that exceeds its autonomy level stops with a non-zero code and no partial changes, per the docs (15). --session-id continues a session, --fork branches one, and --worktree isolates parallel runs (16). Headless runs are read-only without flags, and TypeScript and Python SDKs wrap the CLI. A run needs a paid Factory account and an API key (13).
Schema & documentation Click +5
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.
Droid CLI 79
Framework reading. The docs index links an OpenAPI file for the Factory public API, which we did not open, and the headless mode has a documented JSON-RPC surface with named methods. droid exec --list-tools --output-format json and droid rules check --json give machine-readable output. We found no published schema for the settings file (15). docs.factory.com/llms.txt lists a Markdown copy of every page (10). The overview says when to use the CLI, and the autonomy table says what each level allows, blocks and suits (16). Autonomy levels, output formats, sandbox modes and MCP server fields are enumerated with types and defaults (12). Examples on every page read, exit codes 0, 1 and 2, and a JSON result with is_error and subtype, with no error catalogue (11). A changelog by CLI version with dates and an RSS feed, 236 entries back to 30 September 2025 (15).
Score by category
| Category | Weight | Click | Droid CLI | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 54 | Droid CLI +19 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 79 | Click +5 |
| Agent ergonomics | 13% | 79 | 72 | Click +7 |
| Security & auth | 14% | 41 | 63 | Droid CLI +22 |
| Payments & pricing | 10% | 15 | 15 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 79 | Droid CLI +54 |
| Transparency & trust | 7% | 44 | 65 | Droid CLI +21 |
| Negative events | ≤15 | 0 | -3 | |
| Total | D 48.6/100 | C 57.8/100 |
Facts side by side
| Fact | Click | Droid CLI |
|---|---|---|
| Kind | HTTP API | Agent harness |
| Vendor | Click AI Labs, Inc. | Factory |
| Hosted endpoint | https://api.useclick.ai/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1 | Proprietary, under Factory's Terms and Conditions. The droid npm package is marked UNLICENSED and the public repository holds documentation only. The Python SDK is Apache-2.0 |
| Tools exposed | 23 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-19 | 2026-11-04 |
| Terms last updated | 2026-10-12 | 2026-07-14 |
| Privacy policy last updated | 2026-10-12 | 2026-08-20 |
| 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 | yes |
| Popularity | none | 49 stars, 7.8k npm/wk |
How the scores have moved
Click
No score change since it was listed.
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.
Droid CLI
droid exec is read-only unless --auto raises the autonomy level, with command rules, an optional kernel-enforced sandbox, JSON output and documented exit codes. No free tier, status page or security.txt was found, the source is closed, usage metrics go to Factory by default, and security fixes ship in release notes without advisories.
Before you call either
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
Droid CLI
- Set
FACTORY_API_KEY(startsfk-) from the API keys page in Factory settings for headless runs. Interactive use signs in through a browser - Start with
droid execand no flags for analysis. Add--auto lowfor edits and--auto mediumfor installs, tests and local commits - Use
--output-format jsonand readis_error,num_turnsandsession_id. Treat a non-zero exit code as failure - Set
sandbox.enabledto true before running on untrusted code. Indroid execa sandbox violation is denied without a prompt - Pin the version in CI with
npm install -g droid@<version>, or setFACTORY_DROID_AUTO_UPDATE_ENABLED=falseon standalone installs, which update themselves. Read each release's Security section before upgrading
Questions
Which is better for AI agents, Click or Droid CLI?
Droid CLI scores 57.8 (C) 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 Droid CLI without installing anything?
Click has a hosted endpoint at https://api.useclick.ai/v1. No hosted endpoint is listed for Droid CLI.
Other comparisons with Click or Droid CLI
- Agent Zero vs Click
- Agent Zero vs Droid CLI
- Aider vs Click
- Aider vs Droid CLI
- Amp vs Click
- Amp vs Droid CLI
- Antigravity CLI vs Click
- Antigravity CLI vs Droid CLI
- Auggie CLI vs Click
- Auggie CLI vs Droid CLI
- AXLR vs Click
- AXLR vs Droid CLI
- boxes.dev vs Click
- boxes.dev vs Droid CLI
- Claude Code vs Click
- Claude Code vs Droid CLI
- 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 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)
- Cline vs Droid CLI
- Conductor vs Droid CLI
- Crush vs Droid CLI
- Cursor CLI vs Droid CLI
- DeepSeek Harness (dsh) vs Droid CLI
- dsh-superagent (DeepSeek) vs Droid CLI
- Devin vs Droid CLI
- Droid CLI vs Pi
- Droid CLI vs Emdash
- Droid CLI vs Friday
- Droid CLI vs Gemini CLI
- Droid CLI vs GitHub Copilot CLI
- Droid CLI vs goose
- Droid CLI vs Harness²
- Droid CLI vs HarnessRouter
- Droid CLI vs Jules
- Droid CLI vs Junie CLI
- Droid CLI vs Kilo Code CLI
- Droid CLI vs Kimi Code CLI
- Droid CLI vs Kiro CLI
- Droid CLI vs Letta
- Droid CLI vs mini-swe-agent
- Droid CLI vs MiniMax Code
- Droid CLI vs Mistral Vibe CLI
- Droid CLI vs Muse Code
- Droid CLI vs OpenAI Agents API
- Droid CLI vs OpenAI Codex
- Droid CLI vs OpenCode
- Droid CLI vs OpenHands
- Droid CLI vs OpenMausBot
- Droid CLI vs Orca
- Droid CLI vs Paseo
- Droid CLI vs Prime Agent
- Droid CLI vs Qoder CLI
- Droid CLI vs Qwen Code
- Droid CLI vs Mirror CLI
- Droid CLI vs Rovo Dev CLI
- Droid CLI vs Sculptor
- Droid CLI vs T3 Code
- Droid CLI vs Traycer
- Droid CLI vs Unstoppable
- Droid CLI vs Verdent
- Droid CLI vs Vibe-Trading
- Droid CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs Droid CLI
- Clawboo vs Droid CLI
- CLI Manager vs Droid CLI
- Droid CLI vs Harness
- Droid CLI vs herdr
- Droid CLI vs Paperclip
- Droid CLI vs Parallax
Machine-readable
- This page as Markdown
/compare/click-agents-vs-droid-cli.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/click-agents.json·/api/v1/tools/droid-cli.json - From a terminal
anchor compare click-agents droid-cli(the CLI) - Over MCP
compare_tools {"a": "click-agents", "b": "droid-cli"}at/mcp, no key