Files

Dylan e3565a3f43 [sandbox] Filter out certain non-sandbox errors (#1804 )

## Summary
Users frequently complain about re-approving commands that have failed
for non-sandbox reasons. We can't diagnose with complete accuracy which
errors happened because of a sandbox failure, but we can start to
eliminate some common simple cases.

This PR captures the most common case I've seen, which is a `command not
found` error.

## Testing
- [x] Added unit tests
- [x] Ran a few cases locally

2025-08-03 13:05:48 -07:00

src

[sandbox] Filter out certain non-sandbox errors (#1804 )

2025-08-03 13:05:48 -07:00

tests

[sandbox] Filter out certain non-sandbox errors (#1804 )

2025-08-03 13:05:48 -07:00

Cargo.toml

feat: stream exec stdout events (#1786 )

2025-08-01 13:04:34 -07:00

prompt.md

Initial planning tool (#1753 )

2025-07-31 20:45:52 +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.