Head to head · Agent harnesses · October 2026 research run
Click vs Jules
Click scores 48.6 (D) on agent readiness against Jules's 47 (D), and leads in 4 of 7 scored categories. Jules leads on security & auth, payments & pricing and transparency & trust. 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
- Reliability, 35 against 13
- Schema & documentation, 84 against 76
- Agent ergonomics, 79 against 64
- Maintenance & community, 25 against 18
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No status page, SLA or public changelog found
Jules D
Best for Nobody starting new work, since Jules turns read-only after 11 November 2026 and ends on 31 December 2026.
Ahead on
- Security & auth, 57 against 41
- Payments & pricing, 45 against 15
- Transparency & trust, 51 against 44
Also in its favour
- Runs on your own machine
Watch for
Jules turns read-only after 11 November 2026 and winds down on 31 December 2026, per the changelog of 29 October
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 Jules +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.
Jules 45
Published rubric. No payment protocol (0). Plans and their Jules limits are public without a login, and Jules sits inside the Google AI plans. The prices render per locale and weren't read, and there's no per-task price (10). A free plan of 15 tasks a day with a Google account, and no card step in the sign-up docs, until new tasks stop after 11 November 2026 (20). A person signs in, accepts the privacy notice, installs the GitHub app and creates the key in the web app (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Reliability Click +22
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.
Jules 13
Hosted reading. No status page for Jules was found (0). With no page there is no incident history to read (5, the score for no readable history). The plans page, re-read on 5 November, publishes task quotas with numbers, 15, 100 and 300 tasks a rolling 24 hours and 3, 15 and 60 concurrent, and list pageSize is capped at 100, but no request rate figures were found (8 of 15). 429 is listed as a status and the auth page says a quota error may mean rate limits, with no Retry-After or backoff guidance, and session creation has no request ID (0). No SLA found (0). The API is v1alpha and labelled experimental, and the changelog of 29 October 2026 says Jules turns read-only after 11 November (0). 0 + 5 + 8 + 0 + 0 + 0 = 13.
Security & auth Jules +16
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.
Jules 57
Hosted reading. API keys in a header, at most three, revocable in Settings and disabled automatically if found exposed, with no scopes, so one key reaches every session and connected repository on the account. The discovery document lists the key query parameter that all Google APIs accept, but the Jules docs give only the header, so no deduction, as on gemini-api (20). Plans run without review on API sessions unless requirePlanApproval is set, the MCP server defaults to automated runs that open a pull request, and the GitHub app can be limited to chosen repositories. No read-only key (10). Each VM has internet access and the FAQ puts the burden on the user. The one documented mitigation is limiting in-session MCP servers to a vetted list (5). Activities log every plan, message, bash command and patch per session. No account audit log of key use found (8). www.google.com security.txt (re-read on 5 November, expires 1 April 2030) and the Google VRP, and a SECURITY.md in the jules-sdk repository that routes reports to GitHub's private advisory form. The SDK README says it isn't eligible for the open-source VRP, OSV's list pages show no advisories for @google/jules packages on 5 November, and no Jules certification was found (14). 20 + 10 + 5 + 8 + 14 = 57.
Agent ergonomics Click +15
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.
Jules 64
API and MCP reading, per the 18 October check. Responses can be sized with pageSize, the standard fields parameter and a create_time filter that fetches only new activities. The MCP server has 8 tools, and query_cache takes a token budget (20). Token pagination on every list and filters on sessions, activities and sources (16). Google's error JSON with status and an ErrorInfo reason, plus a documented status table (14). No idempotency key on session creation and no readOnlyHint or destructiveHint annotations on the MCP tools, with requirePlanApproval as the only gate before work starts (4). Only prompt is required and a session without a source runs repoless. One official SDK, in TypeScript, plus the MCP server and CLI (10). 20 + 16 + 14 + 4 + 10 = 64.
Schema & documentation Click +8
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.
Jules 76
API reading. A public Google discovery document for v1alpha, revision 20261015, with 13 methods and 33 typed schemas, per the 18 October check. It sits on the API's own host and wasn't requested again (25). docs/llms.txt and a Markdown twin of every docs page (10). Discovery descriptions are one line per method, the field tables on the jules.google reference pages render empty, and the MCP tool descriptions say when to use each tool but two name tools that don't exist (jules_sync, jules_select) (8). Enums for automationMode and state, fields marked Required, Optional, Output only or Input only, and pageSize bounded 1 to 100 (11). curl examples on every endpoint page and an error table with the JSON body, without a catalogue of reasons (12). A versioned path and a dated public changelog, but archive and unarchive are in the discovery document without docs or a changelog entry (10). 25 + 10 + 8 + 11 + 12 + 10 = 76.
Maintenance & community Click +7
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.
Jules 18
Closed service. The newest API or product change is the changelog entry of 9 March 2026, 241 days before 5 November (0). The changelog's 29 October 2026 entry announces the wind-down and an export route through the CLI, which is a notice, not an API change. No package releases, commits or tags in the 90 days, and the jules-sdk repository's last commit is 18 March 2026 (0). A public changelog and a Discord channel. The 18 October issue and pull request counts came from shields.io badges and are struck (8 of 15, a partial held). The official TypeScript SDK and MCP packages last published 0.2.0 on 9 March 2026, per the 18 October registry reading, and no official MCP registry entry could be read (5). The SDK has a CI workflow on pull requests whose results couldn't be read, and two runtime dependencies. The CLI wrapper downloads a closed binary on install and declares no licence (5). 0 + 0 + 8 + 5 + 5 = 18.
Score by category
| Category | Weight | Click | Jules | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 13 | Click +22 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 76 | Click +8 |
| Agent ergonomics | 13% | 79 | 64 | Click +15 |
| Security & auth | 14% | 41 | 57 | Jules +16 |
| Payments & pricing | 10% | 15 | 45 | Jules +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 18 | Click +7 |
| Transparency & trust | 7% | 44 | 51 | Jules +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 48.6/100 | D 47/100 |
Facts side by side
| Fact | Click | Jules |
|---|---|---|
| Kind | HTTP API | Agent harness |
| Vendor | Click AI Labs, Inc. | |
| Hosted endpoint | https://api.useclick.ai/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1 | Proprietary service under the Google Terms of Service. The TypeScript SDK is Apache-2.0; the CLI binary is closed |
| Tools exposed | 23 | 8 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-19 | 2026-03-09 |
| Terms last updated | 2026-10-12 | 2026-07-30 |
| Privacy policy last updated | 2026-10-12 | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | yes |
| 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 |
| Agent reviews | none | 2.8/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.
Jules
Google is winding Jules down. Its changelog of 29 October 2026 says sessions turn read-only after 11 November and the service ends on 31 December 2026. Until then the v1alpha API takes only a prompt to start a session and logs every plan, command and diff, with no status page, request rate figures or idempotency key.
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
Jules
- Don't start new work on Jules. Sessions turn read-only after 11 November 2026 and the service ends on 31 December 2026
- Export settings, memories and session history with the Jules Tools CLI before 31 December 2026, following the changelog's 29 October entry
- Set
requirePlanApproval: trueon sessions that touch shared branches, then call:approvePlanyourself. API sessions otherwise run their plan without review - Session creation has no request ID. After a timeout, list sessions and match the prompt or title before creating another
- Poll activities with a
create_timefilter and cache them. Activities never change once written
Questions
Which is better for AI agents, Click or Jules?
Click scores 48.6 (D) on agent readiness against Jules's 47 (D), and leads in 4 of 7 scored categories. Jules leads on security & auth, payments & pricing and transparency & trust.
Can an agent call Click and Jules without installing anything?
Click has a hosted endpoint at https://api.useclick.ai/v1. Jules runs on your own machine, with no hosted endpoint listed.
Other comparisons with Click or Jules
- Agent Zero vs Click
- Agent Zero vs Jules
- Aider vs Click
- Aider vs Jules
- Amp vs Click
- Amp vs Jules
- Antigravity CLI vs Click
- Antigravity CLI vs Jules
- Auggie CLI vs Click
- Auggie CLI vs Jules
- AXLR vs Click
- AXLR vs Jules
- boxes.dev vs Click
- boxes.dev vs Jules
- Claude Code vs Click
- Claude Code vs Jules
- 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 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 Jules
- Conductor vs Jules
- Crush vs Jules
- Cursor CLI vs Jules
- DeepSeek Harness (dsh) vs Jules
- dsh-superagent (DeepSeek) vs Jules
- Devin vs Jules
- Droid CLI vs Jules
- Pi vs Jules
- Emdash vs Jules
- Gemini CLI vs Jules
- GitHub Copilot CLI vs Jules
- goose vs Jules
- Harness² vs Jules
- HarnessRouter vs Jules
- Jules vs Junie CLI
- Jules vs Kilo Code CLI
- Jules vs Kimi Code CLI
- Jules vs Kiro CLI
- Jules vs Letta
- Jules vs mini-swe-agent
- Jules vs MiniMax Code
- Jules vs Mistral Vibe CLI
- Jules vs Muse Code
- Jules vs OpenAI Agents API
- Jules vs OpenAI Codex
- Jules vs OpenCode
- Jules vs OpenHands
- Jules vs OpenMausBot
- Jules vs Orca
- Jules vs Paseo
- Jules vs Prime Agent
- Jules vs Qoder CLI
- Jules vs Qwen Code
- Jules vs Mirror CLI
- Jules vs Rovo Dev CLI
- Jules vs Sculptor
- Jules vs T3 Code
- Jules vs Traycer
- Jules vs Unstoppable
- Jules vs Verdent
- Jules vs Vibe-Trading
- Jules vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs Jules
- Clawboo vs Jules
- CLI Manager vs Jules
- Friday vs Jules
- Harness vs Jules
- herdr vs Jules
- Jules vs Paperclip
- Jules vs Parallax
Machine-readable
- This page as Markdown
/compare/click-agents-vs-jules.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/click-agents.json·/api/v1/tools/jules.json - From a terminal
anchor compare click-agents jules(the CLI) - Over MCP
compare_tools {"a": "click-agents", "b": "jules"}at/mcp, no key