Windows sandbox blocks local image inputs with split writable roots

Open 💬 1 comment Opened Jul 15, 2026 by aswansong

What version of the Codex App are you using (From “About Codex” dialog)?

26.707.30751

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Local image inputs are blocked by the Windows sandbox, preventing image inspection and built-in image generation with local reference images.

Expected behavior:
Codex should be able to read a local image reference from the current workspace or an approved local pet directory, then use it with view_image and built-in image generation.

Actual behavior:
With this configuration:

[windows]
sandbox = "unelevated"
sandbox_private_desktop = true

view_image and built-in image generation fail before reading the image with:

windows unelevated restricted-token sandbox cannot enforce split writable root sets directly; refusing to run unsandboxed

The task has multiple writable roots (workspace, visualizations, and temporary directories), which appears to trigger the failure.

I also tested:

[windows]
sandbox = "elevated"
sandbox_private_desktop = true

and then:

[windows]
sandbox = "elevated"
sandbox_private_desktop = false

After restarting Codex, image inspection still failed with:

windows sandbox failed: helper_unknown_error: setup refresh had errors

Impact:
This blocks local visual-reference workflows, including upgrading an existing Codex pet with look directions. The issue occurs even when the image is copied into the current workspace.

No private image content needs to be attached to reproduce this.

What steps can reproduce the bug?

Feedback ID: 019f6613-9a5b-7fa2-91cc-8ccd1d45225a

What is the expected behavior?

Codex should allow a local image file from the current workspace or an approved local directory to be inspected with view_image and used as a reference by built-in image generation.

This should work even when the task has multiple writable roots, without requiring full-access mode or disabling sandboxing.

Additional information

This issue blocks a real local workflow: upgrading an existing Codex pet while preserving its visual identity from a local spritesheet reference.

The source image is valid and can be read by normal local tools. The failure happens before the image is read, during Windows sandbox setup.

I tested both unelevated and elevated Windows sandbox modes. Please do not require users to use danger-full-access mode as a workaround.

Feedback ID: 019f6613-9a5b-7fa2-91cc-8ccd1d45225a

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗