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

Files

T

Michael Bolin fa4cac1e6b fix: introduce AbsolutePathBuf and resolve relative paths in config.toml (#7796 )

This PR attempts to solve two problems by introducing a
`AbsolutePathBuf` type with a special deserializer:

- `AbsolutePathBuf` attempts to be a generally useful abstraction, as it
ensures, by constructing, that it represents a value that is an
absolute, normalized path, which is a stronger guarantee than an
arbitrary `PathBuf`.
- Values in `config.toml` that can be either an absolute or relative
path should be resolved against the folder containing the `config.toml`
in the relative path case. This PR makes this easy to support: the main
cost is ensuring `AbsolutePathBufGuard` is used inside
`deserialize_config_toml_with_base()`.

While `AbsolutePathBufGuard` may seem slightly distasteful because it
relies on thread-local storage, this seems much cleaner to me than using
than my various experiments with
https://docs.rs/serde/latest/serde/de/trait.DeserializeSeed.html.
Further, since the `deserialize()` method from the `Deserialize` trait
is not async, we do not really have to worry about the deserialization
work being spread across multiple threads in a way that would interfere
with `AbsolutePathBufGuard`.

To start, this PR introduces the use of `AbsolutePathBuf` in
`OtelTlsConfig`. Note how this simplifies `otel_provider.rs` because it
no longer requires `settings.codex_home` to be threaded through.
Furthermore, this sets us up better for a world where multiple
`config.toml` files from different folders could be loaded and then
merged together, as the absolutifying of the paths must be done against
the correct parent folder.

fa4cac1e6b · 2025-12-09 17:37:52 -08:00

History

src

fix: introduce AbsolutePathBuf and resolve relative paths in config.toml (#7796 )

2025-12-09 17:37:52 -08:00

templates

chore: enable parallel tc (#7589 )

2025-12-09 17:00:56 +00:00

tests

feat: shell snapshotting (#7641 )

2025-12-09 18:36:58 +00:00

Cargo.toml

fix: introduce AbsolutePathBuf and resolve relative paths in config.toml (#7796 )

2025-12-09 17:37:52 -08:00

gpt_5_1_prompt.md

chore(core) Update shell instructions (#6679 )

2025-11-17 13:05:15 -08:00

gpt_5_codex_prompt.md

chore(core) Update shell instructions (#6679 )

2025-11-17 13:05:15 -08:00

gpt-5.1-codex-max_prompt.md

feat: arcticfox in the wild (#6906 )

2025-11-19 16:31:06 +00: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

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.