18 people reported

All time, since Sep 30, including 9 thumbs-up on GitHub.

Cloud thread follow-ups fail

“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/issues/13086/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

Quiet. No reports and thumbs-up in the last two weeks, down from 11 a week at the late-September peak.

Follow-ups to cloud threads fail AbsolutePathBuf validation on Windows. History of the durable/cloud chat stays readable, but turn/start fails before a new turn starts; thread/fork also fails.

Is this your bug?

File my report
Where
Windows desktop app
Error text
invalid turn/start params: AbsolutePathBuf deserialized without a base path
Versions
0.162.0 to 26.930.21537
Platforms
Windows
How bad
Breaks a normal workflow.

Part of: Task follow-ups fail to submit3 bugs

  1. Follow-up messages fail with AbsolutePathBuf error on Windows19 people
  2. Managed cloud thread rejects messages6 people

Not quite your bug?

  1. Dot cannot read local threads57 people
  2. MXC launcher browser init failure38 people

Original reports9, newest first

  1. Windows dot-delegated tasks: cross-thread AbsolutePathBuf failure and MXC Computer Use startup differential diagnosticsOn GitHub#54455
  2. Cloud task message submission fails with AbsolutePathBuf deserialized without a base pathOn GitHub#54308
  3. Cloud coordinator on Windows rejects turn/start with mixed POSIX/Windows cwd while delegated local execution succeedsOn GitHub#51583
  4. Can’t talk to Workers created by DotOn GitHub#51012
  5. Windows desktop: durable chat turn/start and thread/fork fail with AbsolutePathBuf deserialized without a base pathOn GitHub#50428
  6. Windows cloud chats: Custom follow-ups fail when a sandbox override is addedOn GitHub#50332
  7. Windows Desktop cloud thread: history reads successfully but turn/start fails AbsolutePathBuf validationOn GitHub#49839
  8. Dot creates Codex tasks with mixed Linux/Windows working paths, causing follow-up turns to failOn GitHub#49753
  9. Windows Native: durable-task follow-ups fail with AbsolutePathBuf; mixed paths and permission-profile correlationOn GitHub#49477

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.