Files

jif-oai 277fc6254e chore: use tokio mutex and async function to prevent blocking a worker (#3850 )

### Why Use `tokio::sync::Mutex`

`std::sync::Mutex` are not _async-aware_. As a result, they will block
the entire thread instead of just yielding the task. Furthermore they
can be poisoned which is not the case of `tokio` Mutex.
This allows the Tokio runtime to continue running other tasks while
waiting for the lock, preventing deadlocks and performance bottlenecks.

In general, this is preferred in async environment

2025-09-18 18:21:52 +01:00

src

chore: use tokio mutex and async function to prevent blocking a worker (#3850 )

2025-09-18 18:21:52 +01:00

templates/compact

feat: context compaction (#3446 )

2025-09-12 13:07:10 -07:00

tests

Make ESC button work when auto-compaction (#3857 )

2025-09-18 15:34:16 +00:00

Cargo.toml

Switch to uuid_v7 and tighten ConversationId usage (#3819 )

2025-09-18 14:37:03 +00:00

gpt_5_codex_prompt.md

chore: update "Codex CLI harness, sandboxing, and approvals" section (#3822 )

2025-09-17 16:48:20 -07:00

prompt.md

Add file reference guidelines to gpt-5 prompt (#3651 )

2025-09-15 08:35:30 -07:00

README.md

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

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

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.