Files

ae dc15a5cf0b feat: accept custom instructions in profiles (#1803 )

Allows users to set their experimental_instructions_file in configs.

For example the below enables experimental instructions when running
`codex -p foo`.
```
[profiles.foo]
experimental_instructions_file = "/Users/foo/.codex/prompt.md"
```

# Testing
- ✅ Running against a profile with experimental_instructions_file works.
- ✅ Running against a profile without experimental_instructions_file
works.
- ✅ Running against no profile with experimental_instructions_file
works.
- ✅ Running against no profile without experimental_instructions_file
works.

2025-08-04 09:34:46 -07:00

src

feat: accept custom instructions in profiles (#1803 )

2025-08-04 09:34:46 -07:00

tests

[sandbox] Filter out certain non-sandbox errors (#1804 )

2025-08-03 13:05:48 -07:00

Cargo.toml

Add a TurnDiffTracker to create a unified diff for an entire turn (#1770 )

2025-08-04 11:57:04 -04:00

prompt.md

Initial planning tool (#1753 )

2025-07-31 20:45:52 +00:00

README.md

fix: support special --codex-run-as-apply-patch arg (#1702 )

2025-07-28 09:26:44 -07: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 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.