Files

Ahmed Ibrahim 0f4fd33ddd Moving token_info to ConversationHistory (#5581 )

I want to centralize input processing and management to
`ConversationHistory`. This would need `ConversationHistory` to have
access to `token_info` (i.e. preventing adding a big input to the
history). Besides, it makes more sense to have it on
`ConversationHistory` than `state`.

2025-10-23 20:30:58 -07:00

src

Moving token_info to ConversationHistory (#5581 )

2025-10-23 20:30:58 -07:00

templates/compact

feat: context compaction (#3446 )

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

tests

feat: end events on unified exec (#5551 )

2025-10-23 18:51:34 +01:00

Cargo.toml

feat: use actual tokenizer for unified_exec truncation (#5514 )

2025-10-23 17:08:06 +01:00

gpt_5_codex_prompt.md

feat: instruct model to use apply_patch + avoid destructive changes (#4742 )

2025-10-04 12:49:50 -07: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

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 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.