Files

Dylan 544980c008 [context] Store context messages in rollouts (#2243 )

## Summary
Currently, we use request-time logic to determine the user_instructions
and environment_context messages. This means that neither of these
values can change over time as conversations go on. We want to add in
additional details here, so we're migrating these to save these messages
to the rollout file instead. This is simpler for the client, and allows
us to append additional environment_context messages to each turn if we
want

## Testing
- [x] Integration test coverage
- [x] Tested locally with a few turns, confirmed model could reference
environment context and cached token metrics were reasonably high

2025-08-14 14:51:13 -04:00

src

[context] Store context messages in rollouts (#2243 )

2025-08-14 14:51:13 -04:00

tests

[context] Store context messages in rollouts (#2243 )

2025-08-14 14:51:13 -04:00

Cargo.toml

Wait for requested delay in rate limit errors (#2266 )

2025-08-13 15:43:54 -07:00

prompt.md

fix: remove behavioral prompting from update_plan tool def (#2261 )

2025-08-13 19:05:13 +00: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.