2 people reported
All time, since Oct 1.
Messages lost in UNC workspaces
“Conversation messages disappear after reopening the same thread in the Codex VS Code extension when the workspace is an SMB/UNC network share.”
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/10323/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
Conversation messages lost after restart in SMB/UNC workspaces. Threads stay listed but content is missing after reopening; logs show "failed to record rollout items" on network shares, in both the VS Code extension and app.
Is this your bug?
File my report- Where
- thread persistence
- Error text
failed to record rollout items: thread-store internal error: permission path cannot be represented losslessly- Versions
- 26.928.31416 to 26.1002.51308
- Platforms
- Windows
- How bad
- Loses work: code or files lost or damaged.
Not quite your bug?
- Follow-up prompts stuck or lost140 people
- Existing conversations fail to load4 people
- Thread history rolls back2 people