The app settings show Integrated terminal shell = PowerShell, but the agent runtime for my thread reports shell=cmd. Because of that, PowerShell commands like Get-Content fail unless they are explicitly wrapped in powershell -Command ....

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

26.306.996.0

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows [Version 10.0.26200.7840] x64

What issue are you seeing?

The app settings show Integrated terminal shell = PowerShell, but the agent runtime for my thread reports shell=cmd.

Because of that, PowerShell-native commands such as Get-Content fail unless they are explicitly wrapped or rewritten for cmd. In my case, this made the configured shell behavior feel inconsistent and confusing.

It is unclear whether the PowerShell setting only affects the visible integrated terminal while agent/tool execution still uses cmd, or whether this is an actual bug.

What steps can reproduce the bug?

Steps to reproduce:

1. Open Codex settings and set Integrated terminal shell to PowerShell.
2. Start a thread.
3. In the thread/runtime context, the shell is reported as cmd.
4. Run a PowerShell-native command such as Get-Content somefile.txt.
5. The command fails as if it is being executed in cmd.

What is the expected behavior?

Expected behavior:
If PowerShell is selected, agent command execution should either use PowerShell consistently, or the app should clearly distinguish between the shell used for the integrated terminal and the shell used for agent/tool execution.

Additional information

_No response_