Export-Clixml: Access to the path is deined

Resolved 💬 5 comments Opened Jan 7, 2026 by jzr-supove Closed Aug 23, 2026

💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.79.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.2-codex high

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

Bunch of "Export-Clixml: Access to the path is deined" errors during codex is working and executing commands

What steps can reproduce the bug?

Just give him a task

What is the expected behavior?

No red errors during execution time

Additional information

I have OhMyPosh installed, and I have this in $PROFILE

 ~  cat $PROFILE
oh-my-posh init pwsh --config ~/oh_my_posh_profile.json | Invoke-Expression
Import-Module -Name Terminal-Icons
$env:POWERSHELL_TELEMETRY_OPTOUT = "1"

View original on GitHub ↗

5 Comments

etraut-openai contributor · 7 months ago

If you're able to repro this, please use the /feedback slash command to upload your logs and session information.

etraut-openai contributor · 7 months ago

Closing for lack of response. If you see this again, please use the /feedback command to file a new issue.

jzr-supove · 7 months ago

Thread ID: 019be1bf-489a-7aa3-9d79-1d851a683ca9

etraut-openai contributor · 7 months ago

Thanks for the upload. Reopening.

etraut-openai contributor · 7 months ago

You mentioned OhMyPosh and Terminal-Icons. Does the problem go away if you disable those?

The error you're seeing is likely because Export-Clixml is writing to a directory (perhaps for caching purposes) outside of the project root directory. The agent sandbox is doing its job and preventing these writes.

If you rely on Export-Clixml for your use case, you could investigate where it is attempting to write and add that directory to the sandbox_workspace_write.writable_roots in your config file.