Codex Desktop delays returning completed parallel shell_command results when mixed with an escalated gh call on Windows

Summary

Codex Desktop on Windows sometimes delays returning already-completed parallel shell_command results for about 60 seconds when local Git commands are run in the same parallel batch as an escalated / approved gh repo view command.

The child commands themselves finish quickly and print their own completion timestamps, but Codex does not return the local Git tool results to the conversation until much later. This looks like a tool result aggregation / return-path delay rather than slow Git or slow GitHub.

Environment

• Product surface: Codex Desktop app, local Windows workspace tools
• OS: Windows 10 Pro, NT 10.0.26200.0
• Shell: PowerShell 7.6.1
• Codex CLI also installed: codex-cli 0.125.0
• Git: git version 2.47.0.windows.2
• GitHub CLI: gh version 2.92.0 (2026-04-28)
• Repository used for reproduction: local Git repository under D:\Control

I do not see the exact Codex Desktop app version in this tool session.

Steps to reproduce

In a Codex Desktop thread on Windows:

1. Run several fast local Git checks in one parallel tool batch, for example:

• git status --short --branch
• git remote -v
• git branch -a
• git status --short --ignored=matching artifacts

1. In the same parallel batch, include a GitHub CLI command that requires an escalated / approved tool call, for example:

• gh repo view VirgilWa/Control --json nameWithOwner,visibility,url,defaultBranchRef

1. Add internal timing and completion timestamps to each command, e.g. PowerShell Measure-Command plus ended=(Get-Date).ToString('o').
2. Compare each command's internal timing with the wall-clock time reported by Codex for the tool result.

Expected behavior

Once each child command exits and its stdout/stderr are available, Codex should return those tool results promptly. Fast local commands should not be held for tens of seconds after they have already printed their completion timestamp.

Actual behavior

The commands themselves complete quickly, but Codex delays returning some local Git tool results for around 60 seconds.

Observed reproduction from one batch:

git_status_ms=45.77
ended=2026-05-09T20:09:01.4825138+08:00

get_remote_ms / git_remote_ms ~= 54.81
ended=2026-05-09T20:09:01.4917569+08:00

git_branch_ms=57.97
ended=2026-05-09T20:09:01.4941221+08:00

git_ignored_ms=56.9
ended=2026-05-09T20:09:01.4938664+08:00

gh_repo_view_ms=722.94
ended=2026-05-09T20:09:05.1209980+08:00

Even though the local Git commands finished around 20:09:01 and the gh command finished around 20:09:05, Codex returned the local Git tool results with about 60 seconds of wall-clock delay.

A previous similar check showed local Git commands internally taking tens of milliseconds, while the parallel tool batch returned after about 71 seconds. Earlier in the same session, a similar mixed parallel batch appeared to wait 300-500 seconds.

Additional checks

• Serial local Git commands were fast:

git status --short --branch  ~= 43-53 ms
git remote -v                ~= 41 ms
git branch -a                ~= 36-44 ms
git ignored status           ~= 43 ms
serial wall time             ~= 210 ms

• Pure parallel local Git commands were also fast:

git_status_ms ~= 64 ms
git_remote_ms ~= 59 ms
git_branch_ms ~= 61 ms
git_ignored_ms ~= 64 ms
parallel batch returned promptly

• gh repo view itself was also fast in the mixed batch, around 723 ms.
• This suggests the problem is not local Git performance and not GitHub CLI / GitHub network latency.
• The pattern appears when a parallel batch mixes ordinary local shell_command calls with an escalated / approved gh call.

Impact

This makes short repository state checks look like they are hanging for about a minute or more, even though all child commands have already completed. It slows down normal Git closeout workflows and makes it difficult to tell whether the underlying command is slow or Codex's tool result aggregation is delayed.

Related public issues

This may be related in category to:

• #6715: fast shell commands appear to hang before output is returned
• #8479: parallel tool calls have response collection issues
• #12709: Codex Desktop tool responses feel delayed during longer MCP-heavy sessions

This report is specifically about Windows Codex Desktop with parallel shell_command results, internal command timings, and an escalated gh repo view call in the same batch.