Codex App opens hundreds of outbound TCP connections when subagents use imagegen skill

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

26.616.32156

What subscription do you have?

pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

When spawning multiple subagents and asking them to use the imagegen skill, the Codex Desktop/App creates a very large number of outbound TCP connections.

In one reproduction, 6 subagents created approximately 700 outbound TCP connections. About 680 of those connections were observed in the ESTABLISHED state. At a moment there were also a burst of connections in SYN_SENT state.

After this happened, external internet provider stopped accepting any connections from my PC for a few minutes.
This looks like a possible connection leak, missing connection pooling/reuse, missing rate/concurrency limiting, or failure to close imagegen-related network connections when multiple subagents invoke the skill concurrently.

Observed result from one run:

6 subagents -> ~700 outbound TCP connections
~680 connections in ESTABLISHED state
burst of SYN_SENT connections observed
no other processes that were actively using network on the device were running, only a few low activity ones in background

What steps can reproduce the bug?

1. Open Codex Desktop/App.
2. Start a task that spawns multiple subagents with imagegen generation prompt.
3. While the subagents are running, observe outbound TCP connections using a system networking tool.

What is the expected behavior?

Codex should not create hundreds of outbound TCP connections for a small number of subagents using imagegen.

Expected behavior would be something like:

• connections are pooled/reused where possible;
• per-agent or global concurrency limits prevent connection explosions;
• failed or pending outbound attempts are bounded;
• connections are closed promptly after imagegen work completes or fails;
• subagent imagegen usage does not cause the host PC to lose connectivity to external providers.

Additional information

_No response_