iceweasel-oai 639a5f6c48 copy command-runner to CODEX_HOME so sandbox users can always execute it (#13413) ...

• Keep Windows sandbox runner launches working from packaged installs by
running the helper from a user-owned runtime location.

On some Windows installs, the packaged helper location is difficult to
use reliably for sandboxed runner launches even though the binaries are
present. This change works around that by copying codex-
command-runner.exe into CODEX_HOME/.sandbox-bin/, reusing that copy
across launches, and falling back to the existing packaged-path lookup
if anything goes wrong.

The runtime copy lives in a dedicated directory with tighter ACLs than
.sandbox: sandbox users can read and execute the runner there, but they
cannot modify it. This keeps the workaround focused on the
command runner, leaves the setup helper on its trusted packaged path,
and adds logging so it is clear which runner path was selected at
launch.

2026-03-04 01:31:37 +00:00

..

src

copy command-runner to CODEX_HOME so sandbox users can always execute it (#13413)

2026-03-04 01:31:37 +00:00

BUILD.bazel

feat: add support for building with Bazel (#8875)

2026-01-09 11:09:43 -08:00

build.rs

Elevated Sandbox 2 (#7792)

2025-12-10 21:23:16 -08:00

Cargo.toml

copy command-runner to CODEX_HOME so sandbox users can always execute it (#13413)

2026-03-04 01:31:37 +00:00

codex-windows-sandbox-setup.manifest

Elevated Sandbox 2 (#7792)

2025-12-10 21:23:16 -08:00

sandbox_smoketests.py

…