Files

Michael Bolin f38ad65254 chore: standardize on ParsedCommand from codex_protocol (#5218 )

Note these two types were identical, so it seems clear to standardize on the one in `codex_protocol` and eliminate the `Into` stuff.

---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed
with [ReviewStack](https://reviewstack.dev/openai/codex/pull/5218).
* #5222
* __->__ #5218

2025-10-15 13:00:22 -07:00

src

chore: standardize on ParsedCommand from codex_protocol (#5218 )

2025-10-15 13:00:22 -07:00

templates/compact

feat: context compaction (#3446 )

2025-09-12 13:07:10 -07:00

tests

test: reduce time dependency on test harness (#5053 )

2025-10-15 09:56:59 +01:00

Cargo.toml

Simplify parallel (#4829 )

2025-10-07 10:12:38 -07:00

gpt_5_codex_prompt.md

feat: instruct model to use apply_patch + avoid destructive changes (#4742 )

2025-10-04 12:49:50 -07:00

prompt.md

Add file reference guidelines to gpt-5 prompt (#3651 )

2025-09-15 08:35:30 -07:00

README.md

add codex sandbox {linux|macos} (#4782 )

2025-10-05 15:51:57 -07:00

review_prompt.md

Review Mode (Core) (#3401 )

2025-09-12 23:25:10 +00:00

README.md

codex-core

This crate implements the business logic for Codex. It is designed to be used by the various Codex UIs written in Rust.

Dependencies

Note that codex-core makes some assumptions about certain helper utilities being available in the environment. Currently, this

macOS

Expects /usr/bin/sandbox-exec to be present.

Linux

Expects the binary containing codex-core to run the equivalent of codex sandbox linux (legacy alias: codex debug landlock) when arg0 is codex-linux-sandbox. See the codex-arg0 crate for details.

All Platforms

Expects the binary containing codex-core to simulate the virtual apply_patch CLI when arg1 is --codex-run-as-apply-patch. See the codex-arg0 crate for details.