GitHub issue #35420 in openai/codex, opened 2026-07-26 by hiroki-tamba-research, records a report that in the ChatGPT Work / Codex surface on Windows, requests repeatedly fail with stream disconnected before completion, that the Windows workspace being used is OneDrive-backed and the OneDrive client is in a degraded state because it reports that the Microsoft 365 subscription payment could not be processed, that Codex cannot complete work in the selected workspace, and that the evidence establishes a strong correlation between a OneDrive-backed workspace, a degraded OneDrive state, and repeated stream disconnections, while not yet proving which layer is the root cause.
Verbatim Excerpts from Cited Records
“In the ChatGPT Work / Codex surface on Windows, requests repeatedly fail with:”
·
openai/codex (issue 35420 opening body, What issue are you seeing? section)
·
2026-07-26T02:13:07Z
·GitHub Issue ↗
“At the same time, the Windows workspace being used is OneDrive-backed, and the OneDrive client is in a degraded state because it reports that the Microsoft 365 subscription payment could not be processed.”
·
openai/codex (issue 35420 opening body, What issue are you seeing? section)
·
2026-07-26T02:13:07Z
·GitHub Issue ↗
“The practical result is that Codex cannot complete work in the selected workspace. This is especially serious when the user believes the project is local, but Windows has resolved the folder through OneDrive.”
·
openai/codex (issue 35420 opening body, What issue are you seeing? section)
·
2026-07-26T02:13:07Z
·GitHub Issue ↗
“It does not yet prove which layer is the root cause. The failure could originate from workspace resolution, file availability, sync-provider behavior, backend request handling, or the interaction among them.”
·
openai/codex (issue 35420 opening body, What issue are you seeing? section)
·
2026-07-26T02:13:07Z
·GitHub Issue ↗
Counter-record: Issue remains open with 37 comments as of 2026-11-07; the API returned all 37. No maintainer response appears in the surveyed thread. Nearly all comments are follow-ups by the original reporter (2026-07-26 to 2026-08-12) documenting further isolation tests; PerikiyoXD (2026-07-31) and itorres008 (2026-08-03) also commented. The most recent comment (2026-11-07, NotoriousPyro) reports a local workaround of editing Codex state files to remove stale OneDrive paths, after which Codex ran noticeably faster; it does not report a maintainer fix. The reporter states in the opening body that the evidence establishes correlation only and does not prove the root cause. The claim documents only the original report, not a verified current state.
Falsification probe: If issue 35420 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.