Windows: missing rollout prevents reopening a task; unable to access approval review
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.911.61220
What subscription do you have?
Unknown
What platform is your computer?
Windows. Exact OS build not yet collected.
What issue are you seeing?
I cannot reopen an existing task in the Codex desktop app on Windows because its rollout JSONL file is missing.
The error returned when reading the task is:
"invalid paginated history lineage for 01a04b9c-99e5-7831-afe2-7a312e7afade: missing source rollout"
A read-only local inspection found that the task metadata and cached history still exist, but the referenced rollout file does not. The cause is unknown; accidental local deletion is possible. I cannot establish that Codex deleted the file.
The task also contained a previous automatic-review denial. I cannot reopen that task to review the denial. Typing "/" or "/approve" in my current desktop task did not show a command picker.
I need guidance on supported history recovery and access to the formal denial-review workflow. I am not requesting that security checks be disabled.
What steps can reproduce the bug?
Observed sequence on my installation:
- Open the Codex desktop app on Windows.
- Select the existing task with ID:
01a04b9c-99e5-7831-afe2-7a312e7afade - Attempt to reopen or resume it.
- The task fails to load because its source rollout is missing.
- In a separate recovery task, type "/" or "/approve" in the composer.
- No command picker appears in the UI I observed.
I do not have a clean reproduction of how the rollout became missing. I have not deleted additional files, modified the history database, or retried the denied production action.
What is the expected behavior?
When a source rollout is missing, show clear recovery options and explain whether retained cached history can be exported or recovered through a supported process.
Clarify whether this desktop version supports /approve and how to access it. If a prior denial cannot be reviewed because its task no longer opens, provide the supported next step.
Preserve existing project files and security restrictions throughout recovery.
Additional information
Feedback was submitted through Help > Feedback.
Feedback ID:
01a0b44f-f35c-7281-a14e-dcfacd01a764
Locally detected CLI version:
0.155.0-alpha.2.6
This is not the confirmed desktop app version.
Project files have been backed up and a local Git baseline was created. Cached conversation excerpts were recovered, but the original task still cannot be reopened.
No credentials, full diagnostic logs, project backups, or private conversation contents are attached.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Windows desktop app's task-reopen flow and the handling of a missing source rollout, using the reported task ID and error as the entry point. Then inspect the observed /approve command-picker behavior and determine what supported recovery or denial-review path can be documented or exposed without weakening security restrictions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100