[Windows / Codex Desktop + VS Code] Intermittent stream disconnects and reconnect failures since Oct 10

Finding: One external report (not reproduced by KFA) says that from 2026-10-10 the Codex Windows desktop app, package version 26.1007.2314.0 on Windows 11 25H2, repeatedly showed Reconnecting and intermittently failed tasks with a stream-disconnected error. The reporter also says the VS Code Codex extension initially worked but later disconnected too (https://github.com/openai/codex/issues/52919). Reported symptoms: ordinary response streams fail intermittently, and remote context compaction fails with the same stream-disconnect wording. The UI error is 'stream disconnected before completion: An error occurred while processing your request.' (https://github.com/openai/codex/issues/52919). Reported local log evidence, from the reporter's read-only analysis of one day: 22 terminal failed-task events across 5 session files (18 response-stream failures, 4 remote compact failures), 261 desktop app_server_connection websocket_error events, 260 reconnect_failed events, 41 chatgpt_pubsub_connection_failed events and 13 pubsub_reconnect_exhausted events. The reporter stresses these are logged events, not distinct failed prompts, and not a complete incident total (https://github.com/openai/codex/issues/52919). Scope: the cross-client observation means the problem should not be treated as desktop-only. The reporter says it could be a shared service path, both clients, or network/proxy routing, and no transport-level comparison established a cause (https://github.com/openai/codex/issues/52919). Maintainer status: the only comment is an automated bot listing possible duplicates (#52731, #52814, #52294). It is not a diagnosis (https://github.com/openai/codex/issues/52919#issuecomment-6099421955). No confirmed cause, verified workaround, fix commit or released fix appears in the supplied sources. Limitations: this is a single user report, the app version came from package metadata and not the About dialog, the VS Code extension version is unknown, and the reporter is on a paid plan with unknown network or proxy setup. Intermittent failure and symptom overlap with related issues do not establish a shared root cause. No actionable fix can be given from this evidence; it is useful mainly for matching the symptom and avoiding assumptions that switching clients resolves it.