The user dialog for permission lists a long path to PowerShell on Windows first, hiding away the actual command

Open 💬 1 comment Opened May 9, 2026 by claell

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

latest

What subscription do you have?

Edu

What platform is your computer?

Windows 11

What issue are you seeing?

I have this problem on Windows:

<img width="1122" height="392" alt="Image" src="https://github.com/user-attachments/assets/2ff111bd-aeef-409b-ac57-fd70e7de4376" />

See option 2. The path to the PowerShell location completely blocks the name of the actually executed command... This renders this option useless for me.

What steps can reproduce the bug?

Have Codex ask for user permission.

What is the expected behavior?

No huge path to C:\... PowerShell location blocking the actual command name, so one can actually see what one would always allow in the future.

Additional information

Recently, this seemed to have gotten a bit better with an update of the app, but I still see this happening sometimes. So I report here for tracking the problem.

I guess this has never been a problem on macOS.

View original on GitHub ↗

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