Codex Windows app repeatedly gets stuck after a completed ripgrep command #32750

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

26.707.51957

What subscription do you have?

Windows 11

What platform is your computer?

Windows 11 24H2, x64

What issue are you seeing?

The Codex Windows app repeatedly becomes stuck after a local ripgrep (rg -n) command has already completed.

The UI remains on the same tool execution step for 30–40+ minutes without producing a response or showing an error.

I confirmed that the underlying command was no longer running:

Get-Process rg -ErrorAction SilentlyContinue

returned no process.

The complete ripgrep output had already been returned in the session, but Codex did not continue to the next reasoning or tool step.

This issue occurred repeatedly throughout the afternoon. Restarting the Codex app and switching models did not resolve it.

What steps can reproduce the bug?

1. Open a local TypeScript/Node.js repository in the Codex Windows app.

2. Ask Codex to perform a deep project analysis or code review.

3. Codex loads project-analysis/code-review skills.

4. Codex executes a broad ripgrep command such as:

   rg -n "pandoc|reference-doc|citeproc|math|formula|table|caption|template|heading..."

5. The command returns a large number of matching lines.

6. The rg.exe process exits successfully.

7. Codex remains stuck on the same tool step indefinitely.

8. Cancelling, restarting the app, and changing models do not reliably prevent recurrence.

What is the expected behavior?

After the local command exits and its output is returned, Codex should continue analyzing the results, execute the next tool step, produce a final response, or display a clear timeout/error message.

Additional information

Diagnostics observed while the issue was occurring:

• No active rg.exe process existed.
• logs_2.sqlite size remained constant at 237445120 bytes.
• logs_2.sqlite-wal size remained constant at 4433152 bytes.
• The WAL modification timestamp changed occasionally, but the file did not grow.
• Restarting the Codex app did not eliminate the issue.
• Switching models did not eliminate the issue.
• The issue appears to happen after a tool returns a large amount of output.