Codex Windows app intermittently hides existing local tasks from the project task list

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

26.707.72221

What subscription do you have?

plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Summary

The Codex Windows desktop app intermittently hides completed local tasks from the sidebar/project task list. The affected task is not deleted or archived: its session file and SQLite record still exist, and the task can still be found through search, direct thread lookup, or a direct thread link. However, it is absent from the visible task list for the project.

Environment

• Product: Codex Windows desktop app
• Codex package version: 26.707.9981.0
• Operating system: Windows 11 Pro, 64-bit
• OS version/build: 10.0.26200 / Build 26200
• Workspace type: Local Git repository project

Frequency

Intermittent, but it occurred at least twice within 24 hours in the same local project.

Affected threads

1. Thread ID: 019f6660-d2c1-7493-be3a-00027f057c02

• Created on July 15, 2026.
• Found missing from the project task list on July 16, 2026.

1. Thread ID: 019f68c3-2244-7761-bde3-8419bd0277e6

• Created at approximately 10:30 on July 16, 2026 (UTC+8).
• Completed at approximately 10:36.
• Found missing from the project task list at approximately 11:32.

Steps that led to the issue

1. Open a local project in the Codex Windows app.
2. Create and complete a task in that project.
3. Navigate to another task or create a new task.
4. Check the expanded project section in the sidebar.
5. The completed task is sometimes missing from the visible task list.
6. Search for the task by keyword or thread ID, or open it through a direct thread link.
7. The task can still be opened and its full content is intact.

Expected behavior

Every unarchived task associated with the project should remain visible in the project's task list. If a task is pinned, it should be visible in a clearly rendered pinned section and should not appear to be lost.

Actual behavior

The task disappears from the visible project task list even though it still exists locally and is not archived. In one occurrence, the affected thread was present in the local pinned-thread-ids state, but the UI did not show it in a pinned section or in the normal project list.

Local diagnostic evidence

• The affected session JSONL file exists and contains the complete task.
• The live state_5.sqlite database contains the affected thread.
• The database value is archived = 0.
• The stored project path is correct.
• Thread search/read can return the task while the sidebar does not display it.
• Removing the unexpected pinned state and refreshing the task metadata caused the backend normal task list to return the task again.
• At 2026-07-16 11:19:50 UTC+8, the desktop log recorded: "Failed to generate thread description" with "Timed out waiting for structured result."

Impact

This makes existing work appear to be deleted and causes repeated time-consuming recovery checks. It also reduces confidence that the sidebar is a complete record of local tasks.

Request

Please investigate synchronization between the local thread database, pinned-thread state, generated thread metadata, and the sidebar/project task list. Please also ensure that a metadata-generation timeout cannot silently prevent an existing task from being displayed.

I can provide redacted screenshots and a narrowly scoped, sanitized log excerpt if needed. I will not attach the complete local state file because it contains unrelated private task history and local paths.

What steps can reproduce the bug?

This is an intermittent Codex Windows desktop UI/state synchronization bug. No code snippet is required to trigger it because it occurs in the Codex task list itself.

Steps to reproduce:

1. Open a local Git repository project in the Codex Windows desktop app.
2. Create a new task and let Codex complete it.
3. Navigate to another task or create another new task.
4. Return to the expanded project section in the sidebar.
5. Observe that the completed task may be missing from the visible project task list.
6. Search for the task by keyword or thread ID, or open it through a direct thread link.
7. Observe that the task still exists, is not archived, and its complete content can still be opened.

Actual behavior:

The task disappears from the visible project task list even though its local session file and SQLite record still exist. In one occurrence, the task was listed in the local pinned-thread state, but it was not displayed in either the pinned section or the normal project task list.

Expected behavior:

Every unarchived task associated with a project should remain visible in that project's task list. If a task is pinned, it should be displayed in a visible pinned section.

Affected session/thread IDs:

• 019f6660-d2c1-7493-be3a-00027f057c02
• 019f68c3-2244-7761-bde3-8419bd0277e6

Occurrence details:

• The second affected task was created at approximately 10:30 on July 16, 2026 (UTC+8).
• It completed at approximately 10:36.
• It was found missing from the sidebar at approximately 11:32.
• The issue occurred at least twice within 24 hours.

Environment:

• Codex Windows desktop app
• Codex package version: 26.707.9981.0
• Windows 11 Pro, x64
• OS version/build: 10.0.26200 / Build 26200
• Time zone: China Standard Time (UTC+8)
• Local Git repository project

Relevant diagnostic evidence:

• The affected session JSONL files still exist.
• The live state_5.sqlite database contains both affected threads.
• Both threads have archived = 0.
• Their stored project paths are correct.
• Thread search/read can return the missing task while the sidebar does not display it.
• At 2026-07-16 11:19:50 UTC+8, the desktop log recorded:

"Failed to generate thread description"
"Timed out waiting for structured result."

Token/context information:

• Token limit usage: Not available.
• Context window usage: Not available.
• This issue occurred after the task had completed and appears to affect local task-list rendering/state synchronization rather than model context handling.

What is the expected behavior?

_No response_

Additional information

_No response_