OpenAI Codex CLI

Open-source terminal coding agent that operates in a user-selected project and can use local or OpenAI-hosted execution.

Score calculation

(5 + 9 + 4 + 5) ÷ 4 = 5.8

4 of six dimensions rated. Unrated dimensions and BDS status are excluded.

Full scoring method ↗

Setup details

The CLI is a harness; model, account policy, and cloud execution are separate.

Energy

↑

OpenAI Codex CLI does not publish service-specific energy or water data; the model and serving provider determine most inference impact.

Reasoning & sources

Codex runs its command loop in a terminal, but the default model call still goes to OpenAI. Local file access is not evidence that inference runs on the developer’s machine, and OpenAI publishes no Codex task energy figure here. If energy matters, use the lightest capable model and ask OpenAI for region- and workload-specific reporting.

No per-task electricity, water, or emissions data, serving-region breakdown, or lifecycle assessment was found for the harness.

OpenAI Codex CLI source repository ↗

Training rights

↑

OpenAI Codex CLI is a harness that connects to models; its sources do not establish a complete rights record for the training data of every model it can use.

Reasoning & sources

Codex CLI uses OpenAI models by default, and account settings determine whether prompts may be used to improve them. The product does not publish a full training-data rights ledger for those models. Choose an API or business route with the needed data controls, and request model-specific provenance if training rights matter to the decision.

The provider and exact model vary by configuration; no complete rights ledger can be inferred from the harness license or provider list.

Privacy

↑

Codex privacy depends on local versus cloud execution and the account’s data-control settings.

Reasoning & sources

The CLI can run commands in your environment, but model inference and cloud tasks still involve OpenAI services. For private work, choose local execution, confirm the applicable account’s training settings, and distinguish local files from cloud sessions.

Plan, selected model/provider, enabled features, and deployment mode can change this assessment.

Openness

↑

Codex CLI repository is Apache-2.0; hosted models and cloud services remain separate.

Reasoning & sources

The Codex CLI is available under Apache-2.0, so users can inspect, modify and redistribute the client. That license does not cover OpenAI’s hosted models or cloud services. The command-line tool and its inference backend have different access terms.

This score covers the harness/editor source only; hosted services, models, data, or enterprise features may remain proprietary.

Worker treatment

↑

OpenAI’s supplier code sets broad labor standards but does not publish worker outcomes. TIME’s investigation reviewed OpenAI–Sama contracts, payslips, and interviews about 2021–22 Kenyan toxic-content labeling; workers described low take-home pay and distress, while Sama disputed workload/counseling claims and OpenAI said Sama managed pay and support. TIME later reported OpenAI said it was unaware of the conditions and no longer worked with Sama; this is a historical contractor case, not evidence of current API annotation conditions.

Reasoning & sources

A documented past supplier episode includes worker reports of low pay and psychological distress, countered by Sama and OpenAI responses; the current supplier code has no public independent outcome audit. This is relevant when deciding whose business to support, while pay and working conditions for the team behind OpenAI Codex CLI remain unestablished. Ask for current worker outcomes for that team and its suppliers.

TIME reported that OpenAI contracted Sama in 2021 for safety labeling and described low pay and psychologically distressing material; OpenAI and Sama disputed parts of the account. That is relevant to OpenAI’s model pipeline, not proof about Codex CLI staff or current suppliers. Ask OpenAI for current vendor, pay, well-being, and grievance evidence.

A documented past supplier episode includes worker reports of low pay and psychological distress, countered by Sama and OpenAI responses; the current supplier code has no public independent outcome audit. This rating describes the company relationship or supplier policy, not a finding about this particular product’s use.

Working conditions for the people building or supporting OpenAI Codex CLI are not established by this company-wide record. The sources do not establish whether OpenAI uses other current annotation vendors, present worker outcomes, or the effectiveness of the supplier code across vendors.

Government & military

↑

OpenAI publicly describes a 2026 classified Department of War agreement with cloud-only deployment, retained safety controls, cleared staff, and contractual limits. It separately says ChatGPT will reach GenAI.mil for unclassified work used by 3 million civilian and military personnel. Both are direct defense deployments; limits are company-reported and not independently audited.

Reasoning & sources

OpenAI reports cloud-only deployment, retained safety controls, cleared staff, and contractual limits; these are meaningful safeguards, but no independent check of enforcement is public. This is relevant when deciding whose business to support. Deployment of OpenAI Codex CLI or this particular model release under those contracts remains unestablished; consider the company relationship separately from the product’s actual use.

OpenAI announced a Department of War agreement for classified deployments and stated restrictions on autonomous weapons and domestic surveillance. This is a direct OpenAI relationship, not evidence that Codex CLI was the operational interface. Buyers can consider the parent-provider relationship and ask which models and tools served the contract.

OpenAI reports cloud-only deployment, retained safety controls, cleared staff, and contractual limits; these are meaningful safeguards, but no independent check of enforcement is public. This rating describes the company relationship or supplier policy, not a finding about this particular product’s use.

Deployment of OpenAI Codex CLI under these contracts is not established. Actual use, oversight effectiveness, and compliance with contract limits are not independently established.

BDS status

↑

We did not find OpenAI among the named targets in the two official BNC campaign lists. This is a limited list check, not BDS approval.

Reasoning & sources

OpenAI is not a named target in the checked lists, but BDS uses selective campaigns, so absence cannot establish a clean record. OpenAI’s April 2026 agreement names Microsoft as its primary cloud partner and a major shareholder, with revenue-share payments to Microsoft through 2030. That is a documented commercial link to a BDS target, not a separate official listing of OpenAI; local use of downloaded weights does not by itself establish a new payment to either company.

This review covers the named targets in the BNC consumer/pressure guide and No Tech campaign, not every BDS campaign, local group, investment or supplier. Lists and ownership can change. A company’s absence from these lists is not an endorsement or proof that it has no relevant relationships.

All sources