[Windows desktop] “Add to Codex” breakout chat exists but is absent from sidebar and cannot be pinned

What issue are you seeing?

In the unified Codex/ChatGPT Windows desktop app, I opened a side/breakout ChatGPT conversation in a new window and chose Add to Codex.

The import appears to succeed: the conversation still exists in the account-level conversation catalog, can be read by its conversation identifier, and can be opened through direct internal navigation. However, it is not visible anywhere in the left sidebar, including the expected Tasks/Recents area. This makes the conversation appear lost.

Attempting to pin it through Codex's task/sidebar operation also fails because the imported object is classified as a ChatGPT conversation rather than a native Codex task:

No Codex thread found for threadId

The result is a conversation that exists and is directly addressable but cannot be discovered or organized through the visible desktop UI.

Platform

• Windows desktop app
• Unified ChatGPT/Codex interface
• Observed: August 31, 2026

Steps to reproduce

1. Open a ChatGPT side/breakout chat in a new window.
2. Choose Add to Codex.
3. Return to the Codex desktop app.
4. Look for the imported conversation in the left sidebar under Pinned, Projects, Tasks, or Recents.
5. Observe that the conversation is absent.
6. Confirm via account-level conversation lookup or direct navigation that the conversation still exists and opens.
7. Attempt to pin/move the imported conversation using the Codex sidebar task operation.
8. Observe that the operation rejects it because it is not considered a Codex thread.

Expected behavior

After Add to Codex, the imported conversation should immediately appear in a clear, visible sidebar location.

The user should also be able to pin it at the top, regardless of whether its backing type is a ChatGPT conversation or a native Codex task. The UI should not expose a unified sidebar while silently applying incompatible organization rules based on hidden object types.

Actual behavior

• Import succeeds.
• Conversation exists and is readable.
• Direct navigation can open it.
• Conversation is absent from the visible sidebar.
• Pinning through Codex task controls fails because the object is classified as ChatGPT rather than Codex.
• The user reasonably believes the conversation was lost.

Requested fix

1. Make every successfully imported breakout chat immediately visible in the sidebar.
2. Allow both ChatGPT conversations and Codex tasks to be pinned and organized from the unified sidebar.
3. If an object cannot be pinned, explain that limitation before Add to Codex, not after import.
4. Add a visible recovery/search route for imported chats whose sidebar indexing fails.
5. Reconcile sidebar state after import so direct-navigation availability and sidebar discoverability cannot diverge.

Related issues

• #35367 discusses confusing separation between ChatGPT conversations, Codex tasks, projects, and side chats in the unified Windows app.
• #38943 and #39233 describe related sidebar/pinning classification problems, but this report is specifically about an Add to Codex breakout chat that exists yet is absent from the sidebar.

Privacy

No private conversation title, content, conversation ID, project name, account identifier, or screenshot is included.

Reproduce the flow in the Windows desktop app by using Add to Codex on a ChatGPT breakout chat, then inspect how the imported conversation is represented in the sidebar and pinning controls. Done means the imported chat is visible immediately, can be pinned or organized, and has a visible recovery route if sidebar indexing fails.