Skip to main content
toolsSource-backed
OpenAI logo

OpenAI Codex CLI

Lightweight, open-source coding agent from OpenAI that runs in your terminal, edits and runs code locally with configurable sandbox and approval modes, and authenticates with a ChatGPT plan or API key.

by OpenAI · submitted by JPette1783·added 2026-06-05·
HarnessCLI
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://developers.openai.com/codex, https://github.com/openai/codex
Brand
OpenAI
Brand domain
developers.openai.com
Brand asset source
brandfetch
Safety notes
Codex CLI runs as a local agent that can edit files and execute commands on your machine., It supports configurable sandbox and approval modes; keep approvals enabled and review proposed actions before allowing them., Lowering approval or sandbox restrictions lets the agent act more autonomously, increasing the risk of unintended changes., Review generated code and commands before running them against important repositories or systems.
Privacy notes
Code and prompts are sent to OpenAI to power the agent under your ChatGPT plan or API key., Data handling follows OpenAI's policies for the plan or API you authenticate with; review them before processing sensitive code., API keys and account credentials should be stored securely and never committed to source control.
Author
OpenAI
Submitted by
JPette1783
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup. Have accounts and credentials ready first.

0/3 ready
Account & credentials1Install & runtime1General1

Safety & privacy surface

Safety & privacy surface

4 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens.

4 areas
  • SafetyLocal filesCodex CLI runs as a local agent that can edit files and execute commands on your machine.
  • SafetyGeneralIt supports configurable sandbox and approval modes; keep approvals enabled and review proposed actions before allowing them.
  • SafetyGeneralLowering approval or sandbox restrictions lets the agent act more autonomously, increasing the risk of unintended changes.
  • SafetyExecution & processesReview generated code and commands before running them against important repositories or systems.
  • PrivacyCredentials & tokensCode and prompts are sent to OpenAI to power the agent under your ChatGPT plan or API key.
  • PrivacyExecution & processesData handling follows OpenAI's policies for the plan or API you authenticate with; review them before processing sensitive code.
  • PrivacyCredentials & tokensAPI keys and account credentials should be stored securely and never committed to source control.

Disclosure: editorial

Safety notes

  • Codex CLI runs as a local agent that can edit files and execute commands on your machine.
  • It supports configurable sandbox and approval modes; keep approvals enabled and review proposed actions before allowing them.
  • Lowering approval or sandbox restrictions lets the agent act more autonomously, increasing the risk of unintended changes.
  • Review generated code and commands before running them against important repositories or systems.

Privacy notes

  • Code and prompts are sent to OpenAI to power the agent under your ChatGPT plan or API key.
  • Data handling follows OpenAI's policies for the plan or API you authenticate with; review them before processing sensitive code.
  • API keys and account credentials should be stored securely and never committed to source control.

Prerequisites

  • A ChatGPT plan (Plus, Pro, Business, Edu, or Enterprise) for plan-based sign-in, or an OpenAI API key.
  • Node.js and npm for the npm install, or Homebrew for the cask install.
  • A terminal on macOS, Linux, or Windows.

Schema details

Install type
copy
Troubleshooting
No
Source repository stats
Scope
Source repo
Tool listing metadata
Pricing
open-source
Disclosure
editorial
Application category
DeveloperApplication
Operating system
macOS, Windows, Linux
Full copyable content
# npm
npm install -g @openai/codex

# Homebrew
brew install --cask codex

About this resource

Overview

OpenAI Codex CLI is a lightweight coding agent that runs in your terminal. It is a local agent from OpenAI that helps with coding tasks on your computer across macOS, Linux, and Windows, and is also available as an IDE integration and a web experience.

It is released under the Apache-2.0 license and written primarily in Rust. The CLI itself is free and open source; inference is billed through your ChatGPT plan or OpenAI API usage.

Features

  • Runs locally in the terminal as a coding agent.
  • Configurable sandbox and approval modes for controlling autonomy.
  • Authenticates with a ChatGPT plan or an OpenAI API key.
  • Also available as IDE integrations (VS Code, Cursor, Windsurf) and on the web.

Use Cases

  • Drive an AI coding agent from the terminal on a local repository.
  • Use an existing ChatGPT plan for coding assistance without separate billing.
  • Run code edits and commands under explicit approval and sandbox controls.

Installation

# npm
npm install -g @openai/codex

# Homebrew
brew install --cask codex

Disclosure

Editorial listing. No paid placement or affiliate relationship. Codex CLI is open source under Apache-2.0; using it requires a paid ChatGPT plan or OpenAI API usage.

Source citations

Add this badge to your README

Show that OpenAI Codex CLI is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/tools/openai-codex-cli.svg)](https://heyclau.de/entry/tools/openai-codex-cli)

How it compares

OpenAI Codex CLI side by side with its closest alternative on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

Lightweight, open-source coding agent from OpenAI that runs in your terminal, edits and runs code locally with configurable sandbox and approval modes, and authenticates with a ChatGPT plan or API key.

Open dossier

Terminal-based agentic AI coding assistant from Charm that works with many LLM providers, uses LSP and MCP for context, manages per-project sessions, and asks permission before running tools by default.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backed
SubmitterJPette1783JPette1783
Install riskReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandOpenAI logoOpenAICrush logoCrush
Categorytoolstools
SourceSource-backedSource-backed
AuthorOpenAICharm
Added2026-06-052026-06-05
Platforms
Harness
Source repo
Safety notesCodex CLI runs as a local agent that can edit files and execute commands on your machine. It supports configurable sandbox and approval modes; keep approvals enabled and review proposed actions before allowing them. Lowering approval or sandbox restrictions lets the agent act more autonomously, increasing the risk of unintended changes. Review generated code and commands before running them against important repositories or systems.Crush executes tools and commands; by default it asks for permission before each tool call. The --yolo flag skips all permission prompts; the project warns to be very careful with it, so avoid it on untrusted work. The crush.json config is trusted code — any $(...) in it runs at load time with your shell's privileges, so review config files before use. LSP and MCP servers can read your codebase and influence agent behavior; only connect servers you trust.
Privacy notesCode and prompts are sent to OpenAI to power the agent under your ChatGPT plan or API key. Data handling follows OpenAI's policies for the plan or API you authenticate with; review them before processing sensitive code. API keys and account credentials should be stored securely and never committed to source control.Your code context and prompts are transmitted to the LLM provider you configure. API keys are read from environment variables or config files and sent to the configured provider; store them as secrets. Crush records pseudonymous usage metrics tied to a device-specific hash; prompts and responses are never collected. Opt out with CRUSH_DISABLE_METRICS=1 or DO_NOT_TRACK=1.
Prerequisites
  • A ChatGPT plan (Plus, Pro, Business, Edu, or Enterprise) for plan-based sign-in, or an OpenAI API key.
  • Node.js and npm for the npm install, or Homebrew for the cask install.
  • A terminal on macOS, Linux, or Windows.
  • An API key from a supported LLM provider such as Anthropic, OpenAI, or a compatible API.
  • A supported terminal on macOS, Linux, Windows (PowerShell or WSL), or BSD.
  • On Linux/BSD, clipboard helpers (wl-copy/wl-paste for Wayland or xclip/xsel for X11) for clipboard features.
Install
Config
Citations
ClaimUnclaimedUnclaimed
Open in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.