3d35cb4619
## Refactor of the `execpolicy` crate To illustrate why we need this refactor, consider an agent attempting to run `apple | rm -rf ./`. Suppose `apple` is allowed by `execpolicy`. Before this PR, `execpolicy` would consider `apple` and `pear` and only render one rule match: `Allow`. We would skip any heuristics checks on `rm -rf ./` and immediately approve `apple | rm -rf ./` to run. To fix this, we now thread a `fallback` evaluation function into `execpolicy` that runs when no `execpolicy` rules match a given command. In our example, we would run `fallback` on `rm -rf ./` and prevent `apple | rm -rf ./` from being run without approval. |
||
|---|---|---|
| .. | ||
| tool_handlers | ||
| codex_tool_config.rs | ||
| codex_tool_runner.rs | ||
| error_code.rs | ||
| exec_approval.rs | ||
| lib.rs | ||
| main.rs | ||
| message_processor.rs | ||
| outgoing_message.rs | ||
| patch_approval.rs | ||