Files

Dylan ea7d3f27bd [core] Stop escalating timeouts (#1853 )

## Summary
Escalating out of sandbox is (almost always) not going to fix
long-running commands timing out - therefore we should just pass the
failure back to the model instead of asking the user to re-run a command
that took a long time anyway.

## Testing
- [x] Ran locally with a timeout and confirmed this worked as expected

2025-08-05 17:52:25 -07:00

src

[core] Stop escalating timeouts (#1853 )

2025-08-05 17:52:25 -07:00

tests

[prompts] Better user_instructions handling (#1836 )

2025-08-04 18:55:57 -07:00

Cargo.toml

chore(deps): bump toml from 0.9.2 to 0.9.4 in /codex-rs (#1815 )

2025-08-04 14:24:19 -07:00

prompt.md

[prompt] Update prompt.md (#1839 )

2025-08-05 00:43:23 -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.