42 people reported
All time, since Sep 30, including 23 thumbs-up on GitHub.
Task follow-ups fail to submit
“invalid turn/start params: 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/themes/183/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
3 bugs in this theme
- Follow-up messages fail with AbsolutePathBuf error on WindowsNo workaround yet19 people
- Cloud thread follow-ups failNo workaround yet18 people
- Managed cloud thread rejects messagesNo workaround yet6 people
What's included
- Windows Desktop send fails with 'invalid turn/start params: AbsolutePathBuf deserialized without a base path' (-32602, invalid_config)
- thread/fork of the same chat fails with the same AbsolutePathBuf message
- Existing managed cloud task rejects follow-ups with 'a managed thread must retain its original environment' on desktop and web
- Error persists after force-quit or moving the working directory; task history stays readable
Not included
- Dot itself failing to create or message tasks with UNKNOWN or Aeon errors
- Dot unable to read existing local threads
Original reports20, newest first
- Windows dot-delegated tasks: cross-thread AbsolutePathBuf failure and MXC Computer Use startup differential diagnosticsOn GitHub#54455
- Windows desktop local task cannot submit messages, then fails to resume (AbsolutePathBuf / no rollout found)On GitHub#54435
- Existing managed cloud thread cannot accept follow-ups: “a managed thread must retain its original environment” on desktop and webOn GitHub#54395
- Cloud task message submission fails with AbsolutePathBuf deserialized without a base pathOn GitHub#54308
- Windows: Codex turn/start fails with AbsolutePathBuf error due to mixed Linux/Windows cwdOn GitHub#54262
- [Codex App] Cloud thread fails across Desktop, Web and Android — original environment mismatch and publishing failureOn GitHub#53459
- 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
- Cloud coordinator on Windows rejects turn/start with mixed POSIX/Windows cwd while delegated local execution succeedsOn GitHub#51583
Show all 20Show only the newest 10
- 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
- Can’t talk to Workers created by DotOn GitHub#51012
- Windows desktop cannot reply to dot-created local tasks: AbsolutePathBuf errorOn GitHub#50697
- Windows desktop: durable chat turn/start and thread/fork fail with AbsolutePathBuf deserialized without a base pathOn GitHub#50428
- Windows cloud chats: Custom follow-ups fail when a sandbox override is addedOn GitHub#50332
- Windows Desktop cloud thread: history reads successfully but turn/start fails AbsolutePathBuf validationOn GitHub#49839
- Dot creates Codex tasks with mixed Linux/Windows working paths, causing follow-up turns to failOn GitHub#49753
- Windows Native: durable-task follow-ups fail with AbsolutePathBuf; mixed paths and permission-profile correlationOn GitHub#49477