2 people reported

All time, since Oct 9.

AppData Unix sockets inaccessible

“On Windows, the Codex desktop app runs the agent's shell, and every process started from it, under the MSIX package's AppData file-system virtualisation.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/10862/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Agent-launched tools cannot access AF_UNIX sockets under AppData. Processes started from the Windows desktop app's agent shell under MSIX AppData virtualisation fail on socket files; external launches succeed.

Is this your bug?

File my report
Where
Windows desktop app
Error text
rename C:/Users/<user>/AppData/Local/Docker/run/sailor-ingest.sock C:/Users/<user>/AppData/Local/Docker/run/sailor-ingest.sock.stale: The file cannot be accessed by the system.
Versions
26.1002.7124.0
Platforms
Windows
How bad
Breaks a normal workflow.

Not quite your bug?

  1. WSL agent commands fail to spawn70 people
  2. exec_command fails with os error 216 people
  3. Sandbox denies path resolution9 people

Original reports2, newest first

  1. Windows Desktop: Codex-launched tools fail to access AppData Unix sockets across multiple runtimesOn GitHub#53886
  2. Windows: Codex app's agent shell runs inside MSIX AppData virtualisation, so Docker Desktop started by the agent crashes (error 1920 on AF_UNIX sockets)On GitHub#52698

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.