GPU access blocked upon starting VSCode already having "Full access" given. A toggle of the permission is needed. #29209

What version of the IDE extension are you using?

26.616.41845

What subscription do you have?

GPT Pro20x

Which IDE are you using?

VSCode

What platform is your computer?

Windows 11 with VSCode and Codex inside WSL

What issue are you seeing?

Before the update today (2026-06-20, JST around 1-6pm), restarting the VSCode with access already in Full access, the GPU can be accessed via WSL.

With the new update, the GPU access by the agent is blocked despite Full access is remained chosen. I checked on my own terminal WSL is working where nvidia-smi reported the GPU.

When the bug happens, the agent said:

The rerun is currently blocked by OS-level GPU access in this shell (nvidia-smi also says GPU access blocked).
In this sandbox, GPU is not exposed: /dev/dxg is missing and nvidia-smi returns “GPU access blocked by the operating system.”

Stopping the run and restarting does not solve the problem.
The solution is to toggle the access from Full access to something else, and then back. This will fix it.

What steps can reproduce the bug?

Set VSCode and Codex to be in Full access mode, confirms GPU is working.
Restart VSCode, open Codex and confirm the access is still Full access.
Ask the agent to check for GPU access, it will say it is blocked by the sandbox, even though Full access is chosen.

What is the expected behavior?

Upon restarting VSCode, the GPU should be accessible without toggling the permission option.

Additional information

No response