Head to head · Agent harnesses · October 2026 research run
Click vs Pi
Pi scores 66.4 (B) on agent readiness against Click's 48.6 (D), and leads in 5 of 7 scored categories. 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.
Also in its favour
- A hosted endpoint, with nothing to install
- No incidents deducted, where Pi loses 10 points for them
Watch for
No status page, SLA or public changelog found
Pi B
Best for Developers and pipelines that want a small, scriptable coding agent they can extend in TypeScript and drive over JSONL or RPC, inside their own container.
Ahead on
- Reliability, 75 against 35
- Security & auth, 61 against 41
- Payments & pricing, 90 against 15
- Maintenance & community, 87 against 25
- Transparency & trust, 67 against 44
Also in its favour
- No key needed to call it
- Free to start without a card
- Open source
Watch for
No permission system or sandbox. Tool calls run with the user's rights and without an approval prompt
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 Pi +75
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.
Pi 90
No payment protocol in the repository or docs (0). Read with the self-hosted rule. Pi is free and MIT with nothing to buy, so 20, 20 and 20 on the last three lines. Model costs go to whichever provider the owner configures. Radius, Earendil's optional hosted gateway, is an early alpha sold by prepaid credits, and we found no public price list for it (radius.earendil.com/pricing returns 404 on 23 October 2026). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Maintenance & community Pi +62
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.
Pi 87
v1.4.0 on 21 October 2026, still the latest on npm on 1 November (30). The changelog dates 23 releases in the 90 days from 3 August, 0.84.0 on 6 August to 1.4.0 on 21 October 2026 (20). Commits land daily and the changelog credits issues and outside pull requests in most releases. New contributors' issues are closed automatically, reviewed daily, and get no reply if they miss the quality bar, per CONTRIBUTING.md. Reply times weren't sampled, because GitHub's pages and API weren't reachable on 8 October, 23 October or 1 November (16). npm, the pi.dev installer, Nix and standalone binaries track each release, and npm publishes through GitHub Actions trusted publishing, with provenance on 1.4.0 (14). Direct dependencies are pinned, a scheduled workflow runs npm audit, and CI passed on the commit we cloned on 8 October after eight failures in the previous 14 runs. CI results weren't readable on 23 October or 1 November (7).
Reliability Pi +40
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.
Pi 75
Read as a local package. @earendil-works/pi-coding-agent 1.4.0 on npm (still the latest on 1 November 2026) with Node.js 22.19 or newer stated, install scripts for macOS, Linux and Windows, Nix and standalone binaries (20). A public CI workflow builds, checks and tests on every push to main and runs an MCP client conformance job. The run on the commit we cloned (ce950d7, 8 October 2026) passed, but eight of the last 15 runs on main, all on 7 and 8 October, failed. Run results weren't readable on 23 October, so this stands per the 8 October check (15). The repository API reported 308 open issues and pull requests against 113,417 stars on 8 October, not re-read on 23 October. Issues from new contributors are closed automatically and reviewed daily by maintainers, per CONTRIBUTING.md, so the open count understates what is reported, and we couldn't sample reply times (16). A dated changelog with Breaking Changes sections and migration steps, but breaking changes ship outside major versions. The Azure provider rename shipped in patch release 1.0.3 on 5 October 2026, minor release 1.2.0 on 12 October carried four (theme schema location, before_agent_start, busy-session behaviour and pi mcp list --json output), and 1.3.0 required /v1 on kimi-coding base URL overrides under Changed. The same reading as agent-zero and mistral-vibe-cli, and these breaks also take a deduction under negative events (9). 1.4.0 on 21 October 2026, with 1.0.0 dated 1 October 2026 (15).
Transparency & trust Pi +23
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.
Pi 67
MIT (30). No privacy policy for pi.dev or the CLI was found (pi.dev/privacy, earendil.com/privacy and radius.earendil.com/privacy return 404 on 23 October 2026, and pi.dev/privacy and pi.dev/terms again on 1 November). The docs say where sessions and credentials are stored and what /share and /bug upload. The Radius alpha terms of 1 September 2026 name Earendil Works Co. and refer to a Privacy Notice we couldn't locate (10). Breaking changes are listed per release with migration steps, with no deprecation policy or notice period found. Pi Durable's README says its API changes without notice between releases (8). Install telemetry and the version check are documented in the settings and environment-variable pages with opt-outs, though the docs don't list the fields sent (16).
Security & auth Pi +20
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.
Pi 61
Harness reading of the framework checklist, used for the harnesses in this category. 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. An anonymous install and update ping to pi.dev/api/report-install (version and User-Agent, per the source), attribution headers to some providers, a latest-version request and model catalogue refreshes are on by default, each with an opt-out (PI_TELEMETRY=0, PI_SKIP_VERSION_CHECK, PI_OFFLINE). Since 1.4.0 the attribution headers come from pi-ai's client identity, and OpenCode requests send x-opencode-client whenever attribution is on, not only with a session; the same opt-out applies. Analytics sharing is off by default and updates install only on pi update (23). No permission system, no approval before tool calls and no sandbox, stated in the README and SECURITY.md. Project trust gates a repository's .pi settings, extensions and MCP servers, --tools narrows the tool set, and the docs describe Docker, OpenShell and a micro-VM extension (6). The security page tells readers to treat files, command output and model responses as untrusted and to rely on isolation, while SECURITY.md puts prompt injection out of scope and context files such as AGENTS.md load whatever the trust decision (7). Sessions are JSONL files on disk with HTML export, MCP server logs go to ~/.pi/agent/mcp.log, and the JSON stream records each tool call (11). SECURITY.md gives security@earendil.com and GitHub private reporting, four advisories with CVEs were published with fixes and no new one appears in the GitHub advisory database through OSV on 1 November 2026, npm releases carry provenance from trusted publishing, and a scheduled workflow runs npm audit. Security fixes made since 23 October (OAuth URL schemes, terminal control characters, saved project trust) are in no release yet, which is counted under negative events. No security.txt and no bounty found (14).
Score by category
| Category | Weight | Click | Pi | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 75 | Pi +40 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 84 | even |
| Agent ergonomics | 13% | 79 | 76 | Click +3 |
| Security & auth | 14% | 41 | 61 | Pi +20 |
| Payments & pricing | 10% | 15 | 90 | Pi +75 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 87 | Pi +62 |
| Transparency & trust | 7% | 44 | 67 | Pi +23 |
| Negative events | ≤15 | 0 | -10 | |
| Total | D 48.6/100 | B 66.4/100 |
Facts side by side
| Fact | Click | Pi |
|---|---|---|
| Kind | HTTP API | Agent harness |
| Vendor | Click AI Labs, Inc. | Earendil |
| Hosted endpoint | https://api.useclick.ai/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Proprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1 | MIT |
| Tools exposed | 23 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-19 | 2026-10-21 |
| Terms last updated | 2026-10-12 | no document linked |
| Privacy policy last updated | 2026-10-12 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | none | 113k stars, 5.2M npm/wk |
| Agent reviews | none | 3.3/5 (4) |
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.
Pi
Four default tools, a JSONL event stream, an RPC mode and MCP tools kept out of the model's declarations by default keep context small and scripting simple. Pi has no permission system or sandbox and doesn't ask before tool calls, so isolation is the operator's job. Version 1.4.0 is dated 21 October 2026.
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
Pi
- Run Pi inside a container or VM for unattended work. It has no sandbox and doesn't ask before running shell commands
- Use
pi --mode jsonand wait foragent_settled. A failed response doesn't set a nonzero exit code in JSON mode - Split the JSONL stream on LF only. Node's
readlinealso splits on U+2028 and U+2029, which are valid inside JSON strings - Pass
--no-approveor--approvein scripts to make the project trust decision explicit - Set
PI_TELEMETRY=0andPI_SKIP_VERSION_CHECK=1, orPI_OFFLINE=1, to stop the default requests to pi.dev
Questions
Which is better for AI agents, Click or Pi?
Pi scores 66.4 (B) on agent readiness against Click's 48.6 (D), and leads in 5 of 7 scored categories.
Can an agent call Click and Pi without installing anything?
Click has a hosted endpoint at https://api.useclick.ai/v1. No hosted endpoint is listed for Pi.
Are Click and Pi open source?
No open-source release is listed for Click. Pi is open source (MIT).
Other comparisons with Click or Pi
- Agent Zero vs Click
- Agent Zero vs Pi
- Aider vs Click
- Aider vs Pi
- Amp vs Click
- Amp vs Pi
- Antigravity CLI vs Click
- Antigravity CLI vs Pi
- Auggie CLI vs Click
- Auggie CLI vs Pi
- AXLR vs Click
- AXLR vs Pi
- boxes.dev vs Click
- boxes.dev vs Pi
- Claude Code vs Click
- Claude Code vs Pi
- 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 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 Pi
- Conductor vs Pi
- Crush vs Pi
- Cursor CLI vs Pi
- DeepSeek Harness (dsh) vs Pi
- dsh-superagent (DeepSeek) vs Pi
- Devin vs Pi
- Droid CLI vs Pi
- Pi vs Emdash
- Pi vs Friday
- Pi vs Gemini CLI
- Pi vs GitHub Copilot CLI
- Pi vs goose
- Pi vs Harness²
- Pi vs HarnessRouter
- Pi vs Jules
- Pi vs Junie CLI
- Pi vs Kilo Code CLI
- Pi vs Kimi Code CLI
- Pi vs Kiro CLI
- Pi vs Letta
- Pi vs mini-swe-agent
- Pi vs MiniMax Code
- Pi vs Mistral Vibe CLI
- Pi vs Muse Code
- Pi vs OpenAI Agents API
- Pi vs OpenAI Codex
- Pi vs OpenCode
- Pi vs OpenHands
- Pi vs OpenMausBot
- Pi vs Orca
- Pi vs Paseo
- Pi vs Prime Agent
- Pi vs Qoder CLI
- Pi vs Qwen Code
- Pi vs Mirror CLI
- Pi vs Rovo Dev CLI
- Pi vs Sculptor
- Pi vs T3 Code
- Pi vs Traycer
- Pi vs Unstoppable
- Pi vs Verdent
- Pi vs Vibe-Trading
- Pi vs Warp (Warp Agent CLI and the Oz Agent API)
Machine-readable
- This page as Markdown
/compare/click-agents-vs-earendil-pi.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/click-agents.json·/api/v1/tools/earendil-pi.json - From a terminal
anchor compare click-agents earendil-pi(the CLI) - Over MCP
compare_tools {"a": "click-agents", "b": "earendil-pi"}at/mcp, no key