Adam Perry @ OpenAI a4ee536f01 Route filesystem reads and writes by their own sandbox permissions (#46122) ...

## Why

Filesystem reads previously required a sandbox whenever writes were restricted, even with full-disk read permission. This made permitted reads depend on sandbox availability.

## What changed

- Select sandboxing independently for reads and writes, allowing full-disk reads directly while keeping restricted operations sandboxed.
- Use the executor's path convention when evaluating full-disk access, including `:slash_tmp` denials.
- Apply read-specific checks to capability discovery and skill resource reads, allowing unrestricted reads on executors without sandboxed discovery support.

## Testing

Add regression tests for direct read APIs, restricted writes and reads, executor-specific permission rules, and capability discovery without sandbox support. Update Windows tests to verify sandbox enforcement through writes.

GitOrigin-RevId: a03844bd1f0ea583bb54326683cddbfdd050119f

2026-09-17 05:09:03 +00:00

..

src

Route filesystem reads and writes by their own sandbox permissions (#46122)

2026-09-17 05:09:03 +00:00

BUILD.bazel

Refactor exec-server filesystem API into codex-file-system (#19892)

2026-04-27 17:43:15 -07:00

Cargo.toml

[codex] exec-server: stream files in chunks (#28354)

2026-06-16 09:50:55 -07:00