Head to head · Agent harnesses · October 2026 research run
Click vs OpenAI Codex
OpenAI Codex scores 77.3 (BB) on agent readiness against Click's 48.6 (D), and leads in every scored category. 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
Watch for
No status page, SLA or public changelog found
OpenAI Codex BB
Best for Teams that want an open-source harness with safe defaults for unattended runs and an optional hosted agent.
Ahead on
- Reliability, 55 against 35
- Schema & documentation, 90 against 84
- Security & auth, 82 against 41
- Payments & pricing, 90 against 15
- Maintenance & community, 87 against 25
- Transparency & trust, 85 against 44
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
- Open source
Watch for
Pre-1.0 at 0.166.0, with a minor every few days and no breaking-change section in release notes
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 OpenAI Codex +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.
OpenAI Codex 90
Harness reading of the published rubric. No payment protocol (0). Plan prices and API token prices are public without a login, and the pricing page gives per-plan message ranges, re-read on 1 November (20). ChatGPT Free and Go include Codex, and Free needs no card (20). --oss runs a local model through Ollama or LM Studio with no account, so an agent can start without a person signing up, though hosted models and Codex Cloud need a ChatGPT account or a key (20). 0 + 20 + 20 + 20 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Maintenance & community OpenAI Codex +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.
OpenAI Codex 87
0.166.0 on 29 October 2026 (30). 36 stable release tags between 5 August and 29 October, from 0.146.1 to 0.166.0 (20). Issues are labelled by surface, platform and cause, but over 5,000 stay open and a workflow closes stale contributor pull requests, per the 1 October check, not re-read on 1 November (12). TypeScript and Python SDKs are in the same repository and built in CI (15). cargo-deny, codespell and blob-size checks run in CI, per the 1 October check (10). 30 + 20 + 12 + 15 + 10 = 87.
Security & auth OpenAI Codex +41
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.
OpenAI Codex 82
Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Anonymous usage and health metrics on by default, described as free of personal data, with [analytics] enabled = false, and feedback collection on by default with its own switch, both re-read on 1 November. Credentials are a ChatGPT login or an API key (20). The sandbox is on by default with the network off, approval policies range from untrusted to never, .git, .agents and .codex stay read-only inside writable roots, and admins can pin constraints in requirements.toml (19). Network off by default locally. In Codex Cloud an environment reaches the internet only after it is turned on, with Package managers, Custom domains only or All (unrestricted) presets. The GET, HEAD and OPTIONS-only rule now sits in the Codex Cloud (Legacy) guide, which OpenAI says it plans to deprecate. The docs keep a worked example of prompt-injection exfiltration (14). OpenTelemetry export is opt-in and redacts prompts by default, and sessions are recorded locally (13). Bugcrowd programme, SECURITY.md and a signed security.txt on openai.com, per the 1 October check, not re-read on 1 November. As on the openai-api and openai-agents-sdk listings, that security.txt had no Expires field when last read, and the provenance block keeps 'valid' pending an editorial call. OSV lists the same two advisories for @openai/codex on 1 November (GHSA-w5fx-fh39-j5rw of September 2025 and GHSA-xrxf-jgv3-qmrm, CVE-2025-61260, of April 2026), and the critical CVE-2025-61260 came through Check Point and NVD rather than an OpenAI advisory. 0.165.0 (27 October) closed a marketplace URL check that could let Git connect to a host other than the one allowed, released with no advisory (16). SOC 2 isn't scored on the framework reading. 20 + 19 + 14 + 13 + 16 = 82.
Transparency & trust OpenAI Codex +41
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.
OpenAI Codex 85
Apache-2.0 for the CLI and SDKs (30). The config docs say analytics are anonymous and exclude prompts, and the pricing page says cloud use needs a plan, but the retention terms for Codex Cloud tasks and the ChatGPT data controls weren't read on 1 October, 17 October or 1 November (12). The changelog at learn.chatgpt.com dates model retirements ahead of time with replacements (GPT-5.4 and GPT-5.4 mini announced on 31 July for 31 August, GPT-5.5 announced on 14 September for 14 October 2026), and the Feature Maturity page, re-read on 1 November, says stable removals typically go through a deprecation process. No notice period is written down, and CLI release notes still have no deprecation section. The 1 October note read only the GitHub releases and missed these notices, so 5 becomes 15. Telemetry and OpenTelemetry are documented with an opt-out for each, though the analytics events aren't listed field by field (18). 30 + 12 + 15 + 18 = 75.
Reliability OpenAI Codex +20
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.
OpenAI Codex 55
Local-package reading. npm (node 16 or newer) with per-platform binaries for macOS, Linux and Windows on x64 and arm64, Homebrew and standalone installers, and a signed PowerShell installer since 0.162.0, per the 17 October check, with 0.166.0 on 29 October the newest tag (20). Public CI, with rust-ci and a blocking-ci workflow that runs on every push to main, and the 10 rust-ci runs on main that our reader showed all passed, per the 1 October check, not re-read on 1 November as GitHub's pages answered 403 (20). Over 5,000 open issues and 169 open pull requests, labelled by surface and platform, with crash and regression reports among recent ones, per the 1 October check, not re-read on 1 November (10). 0.x minors every few days, and release notes for 0.164.0 to 0.166.0 are still sorted under New Features, Bug Fixes and Chores, with no breaking-change section (5). 0.166.0, pre-1.0 (0). 20 + 20 + 10 + 5 + 0 = 55. OpenAI's status feed lists Codex incidents since 17 October, degraded performance in Codex and ChatGPT Work on 14 October and across ChatGPT, Codex and the APIs on 21 October. The local-package reading doesn't score them.
Schema & documentation OpenAI Codex +6
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.
OpenAI Codex 90
Framework reading. A JSON Schema for config.toml in the repository (codex-rs/core/config.schema.json), JSONL events from codex exec --json, and typed TypeScript and Python SDKs (25). llms.txt at learn.chatgpt.com with a Markdown twin for every page, re-read on 1 November (10). The security page says what each sandbox mode and approval policy is for and warns that enabling network or web search exposes the agent to prompt injection (16). Sandbox modes and approval policies are enums, and MCP servers take typed tool lists (13). Examples throughout, and --output-schema validates the final message. The non-interactive page names the event types, turn.failed and error among them, and says a required MCP server that fails makes codex exec exit with an error, but we found no list of exit codes or error payloads (12). Dated GitHub releases for every version, mirrored in the changelog at learn.chatgpt.com, which runs to 0.166.0 on 29 October (14). 25 + 10 + 16 + 13 + 12 + 14 = 90.
Score by category
| Category | Weight | Click | OpenAI Codex | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 55 | OpenAI Codex +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 90 | OpenAI Codex +6 |
| Agent ergonomics | 13% | 79 | 80 | OpenAI Codex +1 |
| Security & auth | 14% | 41 | 82 | OpenAI Codex +41 |
| Payments & pricing | 10% | 15 | 90 | OpenAI Codex +75 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 87 | OpenAI Codex +62 |
| Transparency & trust | 7% | 44 | 85 | OpenAI Codex +41 |
| Negative events | ≤15 | 0 | -2 | |
| Total | D 48.6/100 | BB 77.3/100 |
Facts side by side
| Fact | Click | OpenAI Codex |
|---|---|---|
| Kind | HTTP API | Agent harness |
| Vendor | Click AI Labs, Inc. | OpenAI |
| Hosted endpoint | https://api.useclick.ai/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | |
| 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 | Apache-2.0 (Codex CLI, its Rust crates and the TypeScript and Python SDKs). Codex cloud is a hosted service under OpenAI's terms |
| Tools exposed | 23 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-19 | 2026-10-29 |
| Terms last updated | 2026-10-12 | couldn't be read |
| Privacy policy last updated | 2026-10-12 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 126k stars |
| Agent reviews | none | 3/5 (2) |
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.
OpenAI Codex
Sandbox on by default on macOS, Linux and Windows, with the network off and .git and .codex read-only. Pre-1.0 at 0.166.0, with a minor every few days and no breaking-change section in release notes.
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
OpenAI Codex
- Run
codex exec --jsonin pipelines, with--output-schemawhen the final message has to parse - Keep the default sandbox, which has the network off.
--yoloremoves both the sandbox and approvals - Replace
gpt-5.5withgpt-6.1-solin saved configs, custom agents and scripts under ChatGPT sign-in. GPT-5.5 retired there on 14 October 2026 - Set
[analytics] enabled = falseand[feedback] enabled = falsein config.toml to keep usage data local - Pin the npm version. A 0.x minor lands every few days
Questions
Which is better for AI agents, Click or OpenAI Codex?
OpenAI Codex scores 77.3 (BB) on agent readiness against Click's 48.6 (D), and leads in every scored category.
Can an agent call Click and OpenAI Codex without installing anything?
Click has a hosted endpoint at https://api.useclick.ai/v1. No hosted endpoint is listed for OpenAI Codex.
Are Click and OpenAI Codex open source?
No open-source release is listed for Click. OpenAI Codex is open source (Apache-2.0 (Codex CLI, its Rust crates and the TypeScript and Python SDKs). Codex cloud is a hosted service under OpenAI's terms).
Other comparisons with Click or OpenAI Codex
- Agent Zero vs Click
- Agent Zero vs OpenAI Codex
- Aider vs Click
- Aider vs OpenAI Codex
- Amp vs Click
- Amp vs OpenAI Codex
- Antigravity CLI vs Click
- Antigravity CLI vs OpenAI Codex
- Auggie CLI vs Click
- Auggie CLI vs OpenAI Codex
- AXLR vs Click
- AXLR vs OpenAI Codex
- boxes.dev vs Click
- boxes.dev vs OpenAI Codex
- Claude Code vs Click
- Claude Code vs OpenAI Codex
- 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 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 OpenAI Codex
- Conductor vs OpenAI Codex
- Crush vs OpenAI Codex
- Cursor CLI vs OpenAI Codex
- DeepSeek Harness (dsh) vs OpenAI Codex
- dsh-superagent (DeepSeek) vs OpenAI Codex
- Devin vs OpenAI Codex
- Droid CLI vs OpenAI Codex
- Pi vs OpenAI Codex
- Emdash vs OpenAI Codex
- Friday vs OpenAI Codex
- Gemini CLI vs OpenAI Codex
- GitHub Copilot CLI vs OpenAI Codex
- goose vs OpenAI Codex
- Harness² vs OpenAI Codex
- HarnessRouter vs OpenAI Codex
- Jules vs OpenAI Codex
- Junie CLI vs OpenAI Codex
- Kilo Code CLI vs OpenAI Codex
- Kimi Code CLI vs OpenAI Codex
- Kiro CLI vs OpenAI Codex
- Letta vs OpenAI Codex
- mini-swe-agent vs OpenAI Codex
- MiniMax Code vs OpenAI Codex
- Mistral Vibe CLI vs OpenAI Codex
- Muse Code vs OpenAI Codex
- OpenAI Agents API vs OpenAI Codex
- OpenAI Codex vs OpenCode
- OpenAI Codex vs OpenHands
- OpenAI Codex vs OpenMausBot
- OpenAI Codex vs Orca
- OpenAI Codex vs Paseo
- OpenAI Codex vs Prime Agent
- OpenAI Codex vs Qoder CLI
- OpenAI Codex vs Qwen Code
- OpenAI Codex vs Mirror CLI
- OpenAI Codex vs Rovo Dev CLI
- OpenAI Codex vs Sculptor
- OpenAI Codex vs T3 Code
- OpenAI Codex vs Traycer
- OpenAI Codex vs Unstoppable
- OpenAI Codex vs Verdent
- OpenAI Codex vs Vibe-Trading
- OpenAI Codex vs Warp (Warp Agent CLI and the Oz Agent API)
Machine-readable
- This page as Markdown
/compare/click-agents-vs-openai-codex.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/click-agents.json·/api/v1/tools/openai-codex.json - From a terminal
anchor compare click-agents openai-codex(the CLI) - Over MCP
compare_tools {"a": "click-agents", "b": "openai-codex"}at/mcp, no key