[Windows][Desktop 26.820.9563.0] Chat mode hides the conversation title and overflow menu behind Work-only rendering gates

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

26.820.9563.0, installed from the Microsoft Store

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Microsoft Windows 11 Pro, version 10.0.26200, x64

What issue are you seeing?

In the unmodified Microsoft Store build, standard Chat conversations do not render the conversation title or the three-dot overflow/action menu at the top of the conversation.

Work conversations render both elements normally.

The issue was observed before making any local diagnostic modifications. Updating to version 26.820.9563.0 and fully restarting the app did not change the behavior.

This prevents standard Chat users from accessing the existing conversation-level actions and makes the Chat and Work interfaces unnecessarily inconsistent.

What steps can reproduce the bug?

1. Launch the unmodified ChatGPT/Codex desktop app on Windows.
2. Open an existing conversation in standard Chat mode.
3. Inspect the header at the top of the conversation.
4. Observe that neither the conversation title nor the three-dot overflow/action menu is rendered.
5. Open a conversation in Work mode.
6. Observe that the title and three-dot menu are rendered there.
7. Fully restart the application and repeat the comparison.
8. Observe that the difference remains.

What is the expected behavior?

Standard Chat should render the existing conversation title and overflow/action menu, as Work does.

If this difference is intentional, it should be documented, and the affected conversation actions should remain accessible elsewhere.

Additional information

The relevant minified bundle in version 26.820.9563.0 is:

webview/assets/chatgpt-conversation-page-B0xndK8z.js

The Work-origin predicate is:

Qe = We === "tpp" || We === "flora"

The header/action row is gated by:

ut = Qe || lt != null || !1

The title has a separate rendering gate:

ln = Qe ? titleComponent : null

A related Chat-to-Work action is gated by:

showHandoff: V && !Ge && (Me || Ae)

I performed an isolated diagnostic experiment on a portable copy while leaving the installed Microsoft Store package unchanged.

Results:

1. Changing only the header rendering gate caused the three-dot menu to appear in standard Chat.
2. Changing only the separate title gate caused the existing title component to appear.
3. Both results were visually confirmed after restarting the portable copy.
4. The ASAR entry and integrity metadata were updated and verified for the diagnostic copy.
5. The original Store package, login state, user profile, settings, and chat history were not modified.

This indicates that the title data and components already exist, but their rendering is suppressed by the Work-origin conditions.

The diagnostic modification is not being proposed as an end-user workaround, and no full app.asar file is attached.

In-app feedback was also submitted with the current session logs.

Feedback session ID:

01a03eaf-6773-7fd0-a82a-03e3e17d743a