Files

Anton Panasenko 9572cfc782 [codex] add developer instructions (#5897 )

we are using developer instructions for code reviews, we need to pass
them in cli as well.

2025-10-30 11:18:31 -07:00

src

[codex] add developer instructions (#5897 )

2025-10-30 11:18:31 -07:00

templates

Delegate review to codex instance (#5572 )

2025-10-29 21:04:25 +00:00

tests

[codex] add developer instructions (#5897 )

2025-10-30 11:18:31 -07:00

Cargo.toml

chore: merge git crates (#5909 )

2025-10-29 12:11:44 +00: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

docs: align sandbox defaults, dedupe sections and improve getting started guide (#5357 )

2025-10-19 16:41:10 -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 support matrix is:

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.