19 people reported
All time, since Oct 3, including 11 thumbs-up on GitHub.
Follow-up messages fail with AbsolutePathBuf error on Windows
“Direct follow-up messages in dot-created Windows tasks fail at turn/start with -32602 invalid_config: "AbsolutePathBuf deserialized without a base path".”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/10471/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Replying in the desktop app to dot-created tasks is rejected at turn/start; the error persists after force-quit.
Is this your bug?
File my report- Where
- Windows desktop app
- Error text
Error submitting message; invalid turn/start params: AbsolutePathBuf deserialized without a base pathPasted in 2 reports- Versions
- 26.1002.51308
- Platforms
- Windows
- How bad
- Breaks a normal workflow. Some reports say it blocks them completely.
Part of: Task follow-ups fail to submit3 bugs
- Cloud thread follow-ups fail18 people
- Managed cloud thread rejects messages6 people
Not quite your bug?
- Follow-up messages cannot be sent40 people
- Follow-up Send hangs3 people
Original reports9, newest first
- Windows desktop local task cannot submit messages, then fails to resume (AbsolutePathBuf / no rollout found)On GitHub#54435
- Windows: Codex turn/start fails with AbsolutePathBuf error due to mixed Linux/Windows cwdOn GitHub#54262
- Windows app: dot-created tasks fail with AbsolutePathBuf; later helper setup failsOn GitHub#51829
- AbsolutePathBuf deserialized without a base path. Cannot send messages in codex chat.On GitHub#51679
- [Windows Desktop 26.930.7945.0] Local task replies/approvals fail with AbsolutePathBuf; two-machine setupOn GitHub#51593
- Error message when i send message in codexOn GitHub#51535
- Windows dot chat cannot send follow-ups: AbsolutePathBuf error persists after force-quitOn GitHub#51469
- [Windows][dots] Desktop follow-up to dot-created task fails: AbsolutePathBuf and mixed cloud/Windows cwdOn GitHub#51049
- Windows desktop cannot reply to dot-created local tasks: AbsolutePathBuf errorOn GitHub#50697