[Windows Desktop 26.901.6511.0] Active Codex task temporarily disappears from sidebar while remaining active

What version of the Codex App are you using?

• Windows package: OpenAI.Codex 26.901.6511.0
• Codex runtime reported in the WSL workspace: codex-cli 0.130.0-alpha.5

What platform is your computer?

• Codex/ChatGPT desktop app for Windows
• Local project running in WSL2
• Ubuntu 22.04, Linux kernel 6.6.114.1-microsoft-standard-WSL2, x86_64

What issue are you seeing?

An active local Codex task temporarily disappeared from the desktop sidebar while the task itself remained alive and could continue accepting messages.

The disappearance happened during a multi-turn, tool-heavy task that used shell commands, PTY input, HTTP requests, and SSH calls to two remote environments. The user described the active chat as having disappeared and could no longer rely on the sidebar to understand whether the work had been lost.

A later read-only check through the supported task inventory showed that the same task still existed with:

• status: active
• its original local project association
• its original WSL working directory
• no archived copy of the task

The task then continued normally after another user message. This suggests a transient desktop sidebar/catalog projection problem rather than transcript deletion.

What steps can reproduce the bug?

The exact reproduction is not yet deterministic. The observed sequence was:

1. Open a local Codex task in a saved project backed by a WSL2 working directory.
2. Run a multi-turn task with several shell commands, PTY input, API calls, and SSH calls to remote hosts.
3. Complete one turn and send a follow-up.
4. Observe that the active chat/task disappears from the Windows desktop sidebar.
5. Continue the same task through a subsequent message.
6. Query the supported task inventory and observe that the task is still present, active, project-associated, and not archived.

What is the expected behavior?

An active task should remain discoverable in the desktop sidebar for the full lifetime of the task.

If sidebar hydration or filtering temporarily fails, the app should reconcile against the canonical task inventory and restore the row automatically without making the user think the conversation was deleted.

Additional information

Work state at the moment continuity became unclear, included here only to identify the turn boundary:

• The assistant had validated a new external AI-provider credential.
• A second provider account had been created in production, local, and remote-development environments.
• The provider records existed and were active, but model binding count was still zero in all three environments.
• No model-routing changes, deployment, or service restart had been performed.

After the sidebar problem was reported, all three environments were checked again and the provider records were still present. This further suggests the Codex task's executed work and transcript state survived even though the sidebar entry became unavailable.

No credentials, task IDs, account identifiers, project names, repository names, absolute user paths, raw transcripts, screenshots, or application logs are included because the task involved sensitive API credentials. Sanitized diagnostics can be provided privately if maintainers identify an appropriate channel.

No source files, tests, or entry points are named. Start by reproducing the Windows desktop sidebar disappearance with an active WSL2 task, then compare the sidebar view with the supported task inventory. Done means an active, non-archived task remains discoverable and is restored if sidebar hydration or filtering temporarily fails.