Corrupted deny_read_acl_state.json causes persistent "apply deny-read ACLs" sandbox failures

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

0.145.0-alpha.18

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?

Codex Desktop on Windows failed to initialize Browser Use and Computer Use.

The sandbox repeatedly failed with the following error:

setup error: apply deny-read ACLs

Caused by:
0: parse deny-read ACL state C:\Users\<user>\.codex\.sandbox\deny_read_acl_state.json
1: expected value at line 1 column 1

The state file existed and was 22 bytes long, but its entire contents consisted of null bytes:

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00

Because Codex kept trying to parse this corrupted file as JSON, all subsequent sandbox initialization attempts failed.

What steps can reproduce the bug?

1. Start Codex Desktop on Windows.
2. Attempt to use Browser Use or Computer Use.
3. Codex fails before browser or screen control starts.
4. Inspect this file:

C:\Users\<user>\.codex\.sandbox\deny_read_acl_state.json

1. The file contains only null bytes instead of valid JSON.
2. Restarting Codex or Windows does not resolve the issue because the same corrupted state file is reused.

Workaround:

1. Fully exit Codex.
2. Rename:

deny_read_acl_state.json

to:

deny_read_acl_state.json.broken

1. Restart Codex.

Codex then regenerates the file as:

{
"principals": {}
}

After regeneration, sandbox initialization succeeds.

What is the expected behavior?

Codex should detect that deny_read_acl_state.json is empty, corrupted, or invalid JSON and automatically recreate it.

A corrupted state file should not permanently block Browser Use and Computer Use across restarts.

Additional information

After renaming the corrupted file and restarting Codex, the following successful log entries appeared:

setup refresh: processed 3 write roots (read roots delegated); errors=[]
read-acl-only mode: applying read ACLs
setup binary completed
read ACL run completed

This suggests that the failure was caused specifically by the corrupted deny_read_acl_state.json file rather than Chrome login, the browser extension, or Windows permissions in general.