Continuing a sidebar conversation in a new task fails with "no rollout found"

What version of the Codex App are you using (From “About Codex” dialog)?

26.721.41059

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

When I use the “Continue in a new task” action on an existing conversation opened from the Codex sidebar, the new task fails to start.

Codex displays the following error:

Error title: 启动任务时出错

Error message:
no rollout found for thread id 019fb099-4395-7262-bc53-b8658a0cda16

This failure occurs with both continuation options:

• “Use this workspace”
• “Use a new worktree”

The conversation then shows that it could not be started, and no usable new task is created.

Screenshots:

<img width="254" height="124" alt="Image" src="https://github.com/user-attachments/assets/1e024e10-9d63-489a-848a-32082e5f53c6" />
<img width="1584" height="574" alt="Image" src="https://github.com/user-attachments/assets/3811864f-bdaf-4c71-b2ed-dae53b0d004f" />
<img width="1946" height="1494" alt="Image" src="https://github.com/user-attachments/assets/cb7bfbd4-52b8-4fa1-9ea9-a5a11f46ae9e" />

What steps can reproduce the bug?

1. Open an existing conversation from the Codex sidebar.
2. Locate a message with the “Continue in a new task” action.
3. Click the action.
4. In the continuation dialog, select “Use this workspace”.
5. Observe that the task fails to start.
6. Repeat the process and select “Use a new worktree”.
7. Observe the same failure and the “no rollout found for thread id” error.

What is the expected behavior?

Both continuation options should successfully continue the selected message in a new task.

The new task should start in the selected workspace or worktree and allow me to continue the conversation normally.

Additional information

• Reproducibility: Every time I try this flow.
• Both “Use this workspace” and “Use a new worktree” fail.
• Thread ID: 019fb099-4395-7262-bc53-b8658a0cda16
• Token limit and context window information were not displayed in the UI.