Windows dot chat cannot send follow-ups: AbsolutePathBuf error persists after force-quit #51469

What version of the Codex App are you using (From “About Codex” dialog)?

Not yet verified.

What subscription do you have?

Not provided.

What platform is your computer?

Windows desktop. Exact Windows version/build not verified.

What issue are you seeing?

I cannot send follow-up messages in an existing dot-associated chat in the ChatGPT/Codex Windows desktop app. Sending a message shows:

Error submitting message; invalid turn/start params: AbsolutePathBuf deserialized without a base path

This is slowing down my entire workflow. Between this failure and the separate environment issue below, I have been unable to make improvements or advance the original work I was doing for hours.

What steps can reproduce the bug?

1. Open an existing dot-associated chat.
2. Submit a follow-up message.
3. Receive the error above.
4. Force-quit ChatGPT using Windows Task Manager.
5. Reopen and resubmit.
6. The same error persists.

What is the expected behavior?

Send follow-ups and continue existing work. Please investigate a recovery path preserving chat history and work.

Additional information

Observed October 6, 2026.

Assistant-mediated continuation could start a turn and browser task reload worked; my direct message submission remains broken. The main conversation with the dot still works, so not every chat is affected.

No app-data reset, chat deletion, or permission weakening has been attempted.

#49477 and #49753 report similar Windows errors, but I have not verified mixed paths or the failing request field in my case and cannot confirm a shared cause.

Separate issue #51434 concerns cloud environment publication/startup and an environment setup chat failing to resume. It is potentially related, but the cause is unknown. This report tracks the distinct dot-chat send error.