Forumics logo Forumics
Issue 01

Back to issue

All Codex known issues

CLAIM C104 Supported 2026-11-12

GitHub issue #59855 in openai/codex, opened 2026-11-06 by ShakhrukhDR, records a report that opening an affected cloud-managed chat from the Codex Desktop sidebar on Windows can show "Failed to resume chat / Invalid request: AbsolutePathBuf deserialized without a base path" before a new message is submitted, while reading the stored conversation can still succeed; the report asks Desktop to resolve workspace paths when resuming cloud-managed chats from Windows and notes which field triggers the error remains unknown.

Verbatim Excerpts from Cited Records
“Opening an affected cloud-managed chat from the Codex Desktop sidebar on Windows can show this error before a new message is submitted.”
— ShakhrukhDR · openai/codex (issue 59855 opening body, Description section) · 2026-11-06T09:00:43Z ·GitHub Issue ↗
“Failed to resume chat”
— ShakhrukhDR · openai/codex (issue 59855 opening body, Description section) · 2026-11-06T09:00:43Z ·GitHub Issue ↗
“Invalid request: AbsolutePathBuf deserialized without a base path”
— ShakhrukhDR · openai/codex (issue 59855 opening body, Description section) · 2026-11-06T09:00:43Z ·GitHub Issue ↗
“Reading the stored conversation can still succeed while resuming it fails.”
— ShakhrukhDR · openai/codex (issue 59855 opening body, Description section) · 2026-11-06T09:00:43Z ·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 30 comments were read. RGBear (2026-11-06) confirms the same error after a desktop app update, with local chats still working and restart not resolving it. chongming1994 (2026-11-06) gives a working/failing version comparison: desktop 26.1029.7803.0 with app-server 0.166.0-alpha.6 works, 26.1103.3517.0 with 0.167.0-alpha.3.2 fails. a215688925-commits (2026-11-07) reports every tested cloud chat affected, while switching the agent environment to WSL lets the same chats resume. Multiple further Windows reports through 2026-11-11 confirm the same error, including David-Streck (2026-11-11) still seeing it on 26.1103.7773 after it started November 6 on 26.1103.3517. klwb360 (2026-11-07) reports reinstalling the system did not resolve it. Manya-84 (2026-11-11) reports a workaround using a new conversation in a specific saved cloud environment. No maintainer fix and no retraction of the report appear in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If GitHub issue #59855 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.

See also: Codex vs Cursor head-to-head comparison on 9bests