Files

pakrym-oai 3b5a5412bb Log cf-ray header in client traces (#3488 )

## Summary
- log the `cf-ray` header when tracing HTTP responses in the Codex
client
- keep existing response status logging unchanged

## Testing
- just fmt
- just fix -p codex-core
- cargo test -p codex-core *(fails:
suite::client::azure_overrides_assign_properties_used_for_responses_url,
suite::client::env_var_overrides_loaded_auth)*

------
https://chatgpt.com/codex/tasks/task_i_68c31640dacc83209be131baf91611cd

2025-09-11 17:42:44 -07:00

src

Log cf-ray header in client traces (#3488 )

2025-09-11 17:42:44 -07:00

tests

Add Compact and Turn Context to the rollout items (#3444 )

2025-09-11 18:08:51 +00:00

Cargo.toml

Unified execution (#3288 )

2025-09-10 17:38:11 -07:00

prompt.md

prompt to read AGENTS.md files (#3122 )

2025-09-04 13:30:12 -07: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.