Get-Content intermittently stalls for minutes on Windows PowerShell while Codex is reading file context

What version of Codex CLI is running?

codex-cli 0.146.0

What subscription do you have?

Plus plan

Which model were you using?

gpt-5.6

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What terminal emulator and version are you using (if applicable)?

Powershell

Codex doctor report

What issue are you seeing?

After updating to the latest Codex CLI version, I started experiencing intermittent stalls when Codex executes PowerShell Get-Content commands to read files.

This occurs during the context-gathering phase, before the agent has finished reading the relevant files and before it begins reasoning about or implementing the requested changes.

The issue is therefore not a long model-reasoning delay. The active tool call itself remains stuck while attempting to read a local file.

The UI shows that Codex is running a command similar to:

Get-Content <file-path>

However, the command may remain in a running state for an unusually long time, despite the same file being readable immediately when the command is executed manually in another PowerShell session.

The stall is intermittent. Some Get-Content calls return normally, while others take approximately 50–80 seconds or several minutes to complete.

What steps can reproduce the bug?

1.Run Codex CLI on Windows using PowerShell.
2.Open a repository containing multiple source files.
3.Ask Codex to inspect or modify code that requires reading existing files.
4.Observe the context-gathering phase.
5.Codex executes one or more PowerShell Get-Content commands.
6.In some cases, the tool call remains in the running state for an unusually long time.
7.During the stall, Codex has not yet completed reading the file context and has not started the main reasoning or implementation phase.
8.Running the same Get-Content command manually in another PowerShell terminal returns immediately.

What is the expected behavior?

Local file reads using Get-Content should complete within a reasonable amount of time.

For normal source files, the command should usually return almost immediately. If the command cannot complete, Codex should fail quickly and report the underlying filesystem, sandbox, or command-runner error.

Additional information

_No response_