Head to head · Agent harnesses · October 2026 research run

Friday vs OpenAI Codex

OpenAI Codex scores 77.3 (BB) on agent readiness against Friday's 65.3 (B), and leads in every scored category. Both do agent harnesses.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

Friday B

Best for A person who already runs several coding CLIs and wants an outside agent to hand work to them and wait on the result.

Also in its favour

  • No key needed to call it
  • Runs on your own machine

Watch for

Version 0.3.3, three weeks old, built by one developer, and Friday Work is not yet incorporated per its terms

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 45
  • Schema & documentation, 90 against 82
  • Security & auth, 82 against 61
  • Payments & pricing, 90 against 60
  • Maintenance & community, 87 against 70
  • Transparency & trust, 85 against 68

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card

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 +30

Friday 60

Scored on the hosted option, as for Orca. No payment protocol (0). Friday Team is priced on request, with no price on the pages read (0). The app is free and MIT licensed with no card (30). The app needs no account or sign-up (30). 0 + 0 + 30 + 30 = 60.

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.

Security & auth OpenAI Codex +21

Friday 61

Harness reading, as for herdr. 127.0.0.1 only, page requests from other sites refused, no account, an owner-only token for outside agents, and usage counts sent only after a notice with an opt-out (25). Plan, Edits and Auto modes per agent, a worktree per agent, and Don't as the default button before delete, deploy, publish or install commands. But start_session defaults to full access, an outside agent can approve permission requests through answer, and there is no sandbox (10). Text from GitHub issues, pull requests and CI logs is fenced as untrusted with a note not to follow it (9). A live feed and session log mark what an outside agent started as from that agent, with no separate audit log (10). SECURITY.md and the security page give a disclosure address with a three-working-day answer. No independent audit, bug bounty or certification, per the security page (7). 25 + 10 + 9 + 10 + 7 = 61.

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.

Maintenance & community OpenAI Codex +17

Friday 70

v0.3.3 on 17 November 2026, one day before the check (30). 36 releases since 26 October 2026 (20). Issues couldn't be read. CONTRIBUTING.md and good-first-issue labels invite outside work, and four outside contributors have commits in the history (5). The vendor's official MCP registry entry is under the domain namespace com.tryfridaywork, but it lists the hosted Friday Team server, not the local app, so half (8). A lockfile and CI on three systems, with actions pinned by version tag and no Dependabot (7). 30 + 20 + 5 + 8 + 7 = 70.

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.

Transparency & trust OpenAI Codex +17

Friday 68

MIT (30). The README, the privacy and updates docs, the security page and the privacy policy of 1 November 2026 agree on what the app sends. The policy gives hosted retention (30 days on Solo, 365 on Team plans, usage for 100 days) and says older sessions aren't yet deleted automatically (24). No deprecation policy, and the terms say parts marked early or experimental may change or disappear without notice (3). Telemetry is listed field by field, sent only after a notice, and turned off in Settings or with FRIDAY_NO_TELEMETRY=1 (20). 30 + 24 + 3 + 20 = 77.

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 +10

Friday 45

Read as local software, as for herdr and Orca. Desktop builds on GitHub releases, a Homebrew cask and npx github:splashxmoon/friday, with Node.js 22 stated (20). .github/workflows/ci.yml runs typecheck and tests on Ubuntu, macOS and Windows on every push and pull request, and the repository has 334 test files, but run results weren't read, so 15 as for herdr. Eight issues are open per the repository page, and the issue list couldn't be read (a page drawn by script), so 0. Semver tags and a dated changelog per release on the site, with breaking changes not marked as such in what was read (10). Version 0.3.3, not 1.0 (0). 20 + 15 + 0 + 10 + 0 = 45.

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 +8

Friday 82

Read on the outside-agent MCP server. Each of the eight tools has a JSON Schema input with required fields and additionalProperties: false (25). llms.txt, llms-full.txt and every page as Markdown with Accept: text/markdown (10). Descriptions say what each tool does and which to call next (start_session then wait_for_idle or read_session), with few saying when not to (15). Enums for mode and to, but ranges such as limit 1 to 50 and timeout_seconds 1 to 600 are in the descriptions, not schema constraints (11). Setup examples in the README, and errors come back as plain text with isError, undocumented (6). Semver tags and a dated public changelog (15). 25 + 10 + 15 + 11 + 6 + 15 = 82.

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

CategoryWeightFridayOpenAI CodexEdge
Reliability16%4555OpenAI Codex +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8290OpenAI Codex +8
Agent ergonomics13%7880OpenAI Codex +2
Security & auth14%6182OpenAI Codex +21
Payments & pricing10%6090OpenAI Codex +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7087OpenAI Codex +17
Transparency & trust7%6885OpenAI Codex +17
Negative events≤150-2
TotalB 65.3/100BB 77.3/100

Facts side by side

FactFridayOpenAI Codex
KindAgent harnessAgent harness
VendorFriday WorkOpenAI
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceMITApache-2.0 (Codex CLI, its Rust crates and the TypeScript and Python SDKs). Codex cloud is a hosted service under OpenAI's terms
Tools exposed8none
Read-only variant documentednoyes
llms.txtyesyes
MCP registrycom.tryfridaywork/friday-worknot listed
Last release2026-11-172026-10-29
Terms last updated2026-11-01couldn't be read
Privacy policy last updated2026-11-01couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity81 stars126k stars
Agent reviewsnone3/5 (2)

How the scores have moved

Verdicts

Friday

Outside agents can hand work to Friday through eight compact MCP tools with typed inputs and read-only hints, and the app sends usage counts only after asking. It is a three-week-old 0.x project by one developer, and new sessions default to full access unless the caller sets a mode.

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

Friday

  1. Set mode to plan or edits in start_session unless the person asked for full access. The default is full
  2. Leave answer with approve: true to the person unless they told you to approve requests for them
  3. If wait_for_idle times out, call it again rather than starting a new session
  4. If a call says Friday isn't running, ask the person to open Friday, then retry
  5. Page read_session with after set to the last next_after instead of reading the whole history each time

OpenAI Codex

  1. Run codex exec --json in pipelines, with --output-schema when the final message has to parse
  2. Keep the default sandbox, which has the network off. --yolo removes both the sandbox and approvals
  3. Replace gpt-5.5 with gpt-6.1-sol in saved configs, custom agents and scripts under ChatGPT sign-in. GPT-5.5 retired there on 14 October 2026
  4. Set [analytics] enabled = false and [feedback] enabled = false in config.toml to keep usage data local
  5. Pin the npm version. A 0.x minor lands every few days

Questions

Which is better for AI agents, Friday or OpenAI Codex?

OpenAI Codex scores 77.3 (BB) on agent readiness against Friday's 65.3 (B), and leads in every scored category.

Are Friday and OpenAI Codex open source?

Yes. Friday is open source (MIT). 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 Friday or OpenAI Codex

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.