AbsolutePathBuf deserialized without a base path. Cannot send messages in codex chat. #51679

Activity

1. lonestarsigns

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on Oct 7, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems

   app-serverIssues involving app server protocol or interfacesIssues involving app server protocol or interfaces

   dotsIssues involving setting up ChatGPT dots or managing their ongoing work.Issues involving setting up ChatGPT dots or managing their ongoing work.

   on Oct 7, 2026
3. github-actions commented on Oct 7, 2026

   

   github-actionsbot

   on Oct 7, 2026 – with GitHub Actions

   Contributor

   More actions

   Potential duplicates detected. Please review them and close your issue if it is a duplicate.

   • Windows dot chat cannot send follow-ups: AbsolutePathBuf error persists after force-quit #51469
   • Error message when i send message in codex #51535
   • [Windows][dots] Desktop follow-up to dot-created task fails: AbsolutePathBuf and mixed cloud/Windows cwd #51049
   • Windows desktop cannot reply to dot-created local tasks: AbsolutePathBuf error #50697
   • Can’t talk to Workers created by Dot #51012

   Powered by Codex Action
4. DanielGladyshev commented on Oct 7, 2026

   

   DanielGladyshev

   on Oct 7, 2026 – with ChatGPT Codex Connector

   More actions

   Same issue on Windows, app version 26.1002.52244 (released 7 October 2026), tested on October 7.

   A dot-created helper failed with:
   invalid turn/start params: AbsolutePathBuf deserialized without a base path

   Stopping the chat also failed. It later completed, but the archived chat had no Delete button.

   I also observed the following during the same session. I haven't established whether these symptoms share a cause:

   • After restarting the app, chats disappeared from my Dots section. They remained readable and unarchived through account tools. Desktop codex://threads/… links reopened them, but they disappeared from the section again after another restart.
   • In a separate existing Work chat, even a basic local command failed before execution with helper_unknown_error: setup refresh had errors. Chat and web access still worked.
   • dot encountered The invoking thread is not attached to an active Aeon when trying to list environments, create a helper, or message a helper. Messaging an existing helper later succeeded, but that helper still reported no browser-control tools, despite the signed-in side browser being visible in the app.

   The dot thread-creation incident was also active during testing: https://status.openai.com/incidents/01M4BK9J2M83R4SSC71D9FXW45

   No local database repairs or app-data resets have been applied.