mirror of https://github.com/pchuan98/codex.git synced 2026-07-01 00:31:56 +08:00

Files

T

Michael Bolin 1e9babe178 fix: PathBuf -> AbsolutePathBuf in ConfigToml struct (#8205 )

We should not have any `PathBuf` fields in `ConfigToml` or any of the
transitive structs we include, as we should use `AbsolutePathBuf`
instead so that we do not have to keep track of the file from which
`ConfigToml` was loaded such that we need it to resolve relative paths
later when the values of `ConfigToml` are used.

I only found two instances of this: `experimental_instructions_file` and
`experimental_compact_prompt_file`. Incidentally, when these were
specified as relative paths, they were resolved against `cwd` rather
than `config.toml`'s parent, which seems wrong to me. I changed the
behavior so they are resolved against the parent folder of the
`config.toml` being parsed, which we get "for free" due to the
introduction of `AbsolutePathBufGuard ` in
https://github.com/openai/codex/pull/7796.

While it is not great to change the behavior of a released feature,
these fields are prefixed with `experimental_`, which I interpret to
mean we have the liberty to change the contract.

For reference:

- `experimental_instructions_file` was introduced in
https://github.com/openai/codex/pull/1803
- `experimental_compact_prompt_file` was introduced in
https://github.com/openai/codex/pull/5959

1e9babe178 · 2025-12-17 12:08:18 -08:00

History

src

fix: PathBuf -> AbsolutePathBuf in ConfigToml struct (#8205 )

2025-12-17 12:08:18 -08:00

templates

Removed experimental "command risk assessment" feature (#7799 )

2025-12-10 09:48:11 -08:00

tests

fix: session downgrade (#8196 )

2025-12-17 10:44:39 -08:00

Cargo.toml

[codex] add otel tracing (#7844 )

2025-12-12 17:07:17 -08:00

gpt_5_1_prompt.md

chore(prompt) Remove truncation details (#7941 )

2025-12-12 20:21:53 +00:00

gpt_5_2_prompt.md

chore(prompt) Remove truncation details (#7941 )

2025-12-12 20:21:53 +00:00

gpt_5_codex_prompt.md

refactoring with_escalated_permissions to use SandboxPermissions instead (#7750 )

2025-12-10 17:18:48 +00:00

gpt-5.1-codex-max_prompt.md

refactoring with_escalated_permissions to use SandboxPermissions instead (#7750 )

2025-12-10 17:18:48 +00:00

prompt.md

chore(prompt) Update base prompt (#7943 )

2025-12-12 20:50:49 +00: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

docs: Fix markdown list item spacing in codex-rs/core/review_prompt.md (#4144 )

2025-10-30 17:39:21 -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 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.