Greptile Summary

This PR adds a call to ensureGlobalUndiciEnvProxyDispatcher() during gateway startup in startGatewayServer, ensuring the undici global dispatcher is switched to EnvHttpProxyAgent early in the process when an env proxy is configured. Previously, this bootstrapping only happened lazily, per caller (e.g., in provider-openai-codex-oauth.ts, minimax-vlm.ts, and per-attempt in attempt.ts), meaning gateway-level HTTP traffic prior to the first agent run could bypass the configured proxy. The placement after the async startup maintenance steps is intentional.

Confidence Score: 5/5

Safe to merge; the change is minimal, idempotent, and well-tested by existing coverage.

Only finding is a P2 suggestion to pair the call with ensureGlobalUndiciStreamTimeouts for timeout consistency during the startup-to-first-run window. This does not block merge — the agent-run path already applies timeouts correctly, and the window without timeouts is narrow and likely idle.

No files require special attention.

This is a comment left during a code review.
Path: src/gateway/server.impl.ts
Line: 597-598

Comment:
**Missing `ensureGlobalUndiciStreamTimeouts` companion call**

The `EnvHttpProxyAgent` installed here has no timeout options set (`bodyTimeout`, `headersTimeout`). In `attempt.ts`, both functions are always called together — `ensureGlobalUndiciEnvProxyDispatcher()` then `ensureGlobalUndiciStreamTimeouts()` — so the agent-run path is fine. However, any gateway-level undici traffic that occurs between startup and the first agent run will go through a proxy dispatcher with no explicit stream timeouts. If that window is expected to be idle, this is acceptable; otherwise, consider pairing the calls here the same way `attempt.ts` does.

```suggestion
  // Ensure the env-based proxy dispatcher runs after startup so outbound traffic uses a consistent network profile.
  ensureGlobalUndiciEnvProxyDispatcher();
  ensureGlobalUndiciStreamTimeouts();
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix(gateway): ensure undici env proxy di..." | Re-trigger Greptile}

Closing this as implemented after Codex automated review.

Current main already implements PR #63490's central gateway env-proxy bootstrap. startGatewayServer now calls a gateway network bootstrap helper at startup, the helper installs the Undici env proxy dispatcher, regression tests cover direct gateway startup with HTTPS_PROXY, and the changelog records the fix under #71833. The account-id hunk from #63490 is also already present on main.

Best possible solution:

Close #63490 as implemented on current main. Keep the maintained gateway startup bootstrap in src/gateway/server-network-runtime.ts/src/gateway/server.impl.ts; any separate decision to apply global Undici stream timeouts at gateway startup should be tracked as a distinct issue because current main keeps timeout tuning on the embedded-attempt path.

What I checked:

• Gateway startup now bootstraps network runtime: startGatewayServer calls bootstrapGatewayNetworkRuntime() immediately at function entry, before config/plugin startup work, covering the gateway-owned startup path that fix(gateway): ensure undici env proxy dispatcher after startup #63490 tried to patch later in server.impl.ts. (src/gateway/server.impl.ts:245, d54d2d6b9b8a)
• Bootstrap helper installs the env proxy dispatcher: bootstrapGatewayNetworkRuntime() delegates to ensureGlobalUndiciEnvProxyDispatcher(), giving direct gateway startup the same env-proxy dispatcher behavior requested by the PR. (src/gateway/server-network-runtime.ts:1, d54d2d6b9b8a)
• Dispatcher helper is guarded and idempotent: ensureGlobalUndiciEnvProxyDispatcher() no-ops when no env proxy is configured, preserves an existing env-proxy dispatcher, and otherwise installs new EnvHttpProxyAgent() best-effort. (src/infra/net/undici-global-dispatcher.ts:91, d54d2d6b9b8a)
• Regression coverage exercises direct gateway startup: The gateway network runtime e2e test clears proxy env, sets HTTPS_PROXY, starts a minimal gateway, and asserts the global dispatcher is an EnvHttpProxyAgent. (src/gateway/server-network-runtime.e2e.test.ts:60, d54d2d6b9b8a)
• Changelog records the maintained fix: The unreleased changelog says direct Gateway startup now bootstraps env proxy dispatching so provider and plugin network requests honor HTTPS_PROXY/HTTP_PROXY before the first embedded agent attempt, referencing fix(gateway): bootstrap env proxy dispatcher at startup #71833. (CHANGELOG.md:185, d54d2d6b9b8a)
• PR's secondary account-id hunk is already present: src/plugin-sdk/account-id.ts already re-exports from ../routing/account-id.js, matching fix(gateway): ensure undici env proxy dispatcher after startup #63490's secondary change. (src/plugin-sdk/account-id.ts:1, d54d2d6b9b8a)

So I’m closing this as already implemented rather than keeping a duplicate issue open.

Codex Review notes: model gpt-5.5, reasoning high; reviewed against d54d2d6b9b8a; fix evidence: commit d54d2d6b9b8a.