mirror of
https://github.com/openai/codex.git
synced 2026-04-27 09:51:03 +03:00
851fcc377b
[codex-generated] ## Updated PR Description (Ready To Paste) ## Problem When a sub-agent thread emits `ShutdownComplete`, the TUI switches back to the primary thread. That was also happening for user-requested exits (for example `Ctrl+C`), which could prevent a clean app exit and unexpectedly resurrect the main thread. ## Mental model The app has one primary thread and one active thread. A non-primary active thread shutting down usually means "agent died, fail back to primary," but during `ExitMode::ShutdownFirst` shutdown means "the user is exiting," not "recover this session." ## Non-goals No change to thread lifecycle, thread-manager ownership, or shutdown protocol wire format. No behavioral changes to non-shutdown events. ## Tradeoffs This adds a small local marker (`pending_shutdown_exit_thread_id`) instead of inferring intent from event timing. It is deterministic and simple, but relies on correctly setting and clearing that marker around exit. ## Architecture `App` tracks which thread is intentionally being shut down for exit. `active_non_primary_shutdown_target` centralizes failover eligibility for `ShutdownComplete` and skips failover when shutdown matches the pending-exit thread. `handle_active_thread_event` handles non-primary failover before generic forwarding and clears the pending-exit marker only when the matching active thread completes shutdown. ## Observability User-facing info/error messages continue to indicate whether failover to the main thread succeeded. The shutdown-intent path is now explicitly documented inline for easier debugging. ## Tests Added targeted tests for `active_non_primary_shutdown_target` covering non-shutdown events, primary-thread shutdown, non-primary shutdown failover, pending exit on active thread (no failover), and pending exit for another thread (still failover). Validated with: - `cargo test -p codex-tui` (pass) --------- Co-authored-by: Josh McKinney <joshka@openai.com>
npm i -g @openai/codex
or brew install --cask codex
Codex CLI is a coding agent from OpenAI that runs locally on your computer.
If you want Codex in your code editor (VS Code, Cursor, Windsurf), install in your IDE.
If you are looking for the cloud-based agent from OpenAI, Codex Web, go to chatgpt.com/codex.
Quickstart
Installing and running Codex CLI
Install globally with your preferred package manager:
# Install using npm
npm install -g @openai/codex
# Install using Homebrew
brew install --cask codex
Then simply run codex to get started.
You can also go to the latest GitHub Release and download the appropriate binary for your platform.
Each GitHub Release contains many executables, but in practice, you likely want one of these:
- macOS
- Apple Silicon/arm64:
codex-aarch64-apple-darwin.tar.gz - x86_64 (older Mac hardware):
codex-x86_64-apple-darwin.tar.gz
- Apple Silicon/arm64:
- Linux
- x86_64:
codex-x86_64-unknown-linux-musl.tar.gz - arm64:
codex-aarch64-unknown-linux-musl.tar.gz
- x86_64:
Each archive contains a single entry with the platform baked into the name (e.g., codex-x86_64-unknown-linux-musl), so you likely want to rename it to codex after extracting it.
Using Codex with your ChatGPT plan
Run codex and select Sign in with ChatGPT. We recommend signing into your ChatGPT account to use Codex as part of your Plus, Pro, Team, Edu, or Enterprise plan. Learn more about what's included in your ChatGPT plan.
You can also use Codex with an API key, but this requires additional setup.
Docs
This repository is licensed under the Apache-2.0 License.