[Windows app] Clearly separate ChatGPT/Work/Codex projects and allow Chat + Codex + terminal in one workspace

App / environment

• Unified ChatGPT/Codex desktop app for Windows
• Windows 10 x64
• ChatGPT Plus
• Observed after the July 2026 desktop update
• Related in-app feedback ID: no-active-thread-019f96e2-91f9-7a72-b294-6748901ffe85

Summary

The unified Windows app now contains normal ChatGPT Projects, local/Codex projects, Chat, Work, Codex, a browser, side panels, a bottom panel, and a terminal. However, the interface does not clearly distinguish these systems and does not allow the components to be combined into a practical workspace.

This creates both navigation problems and unnecessary mode/usage tradeoffs.

1. ChatGPT Projects and Codex/local projects are visually ambiguous

Normal cloud ChatGPT Projects are available in the app, but local/Codex projects are also shown in the Projects area without a clear project-type label.

This becomes especially confusing when both systems use the same project name. For example, I have a project named Nivis in both ChatGPT and Codex. The sidebar provides no meaningful way to tell which one I am opening. I only realised that both project systems were present because another project, Esca, happens to use different names in ChatGPT and Codex.

The app already supports project colours and custom icons, including a distinct code icon. When the user has not applied a custom appearance, the app should automatically use different defaults for each project type, such as:

• ChatGPT Project: ChatGPT-specific icon
• Work: document/Work icon
• Codex/local project: code icon

Custom user choices should continue to override these defaults.

2. Conversation ordering differs between the Windows app and the web app

The same ChatGPT Project does not present its conversations in the same order across the Windows app and chatgpt.com.

In the Esca project, the most recent pinned conversation appears at the top of the project on the web. In the Windows app, it remains lower in the project conversation list and is also shown separately under the global Pinned section.

This makes it unclear whether project conversations are ordered by recency, pin status, creation date, or another rule. The ordering and pinning behaviour should be consistent and predictable across clients.

3. The project hierarchy should separate ChatGPT, Work, and Codex

A clearer structure would be one overarching project with mode-specific subfolders, for example:

Nivis
├─ ChatGPT
├─ Work
└─ Codex

Each subfolder should contain only the conversations created in that mode. This would preserve a unified project while making the source, purpose, and usage implications of every conversation clear.

At minimum, the sidebar needs explicit project-type badges, distinct default icons, separate sections, and filters for:

• Cloud ChatGPT Projects
• Local/Codex projects
• ChatGPT conversations
• Work conversations
• Codex tasks

4. Terminal and bottom-panel commands silently do nothing in Chat mode

While a normal ChatGPT conversation is active, the commands Toggle Bottom Panel and Open Terminal do nothing.

There is no explanation, and the commands remain visible and selectable. This makes the app appear broken.

At minimum, unavailable actions should be disabled or explain why they are unavailable. Preferably, these commands should work in Chat mode:

• Toggle Bottom Panel should open the bottom panel.
• Open Terminal should open a terminal tab in that panel.
• The terminal should be able to use the local folder associated with the current project, subject to normal permission controls.

5. Codex side chat cannot open a normal ChatGPT conversation

Codex mode can theoretically open a side chat, but that side chat is not a normal ChatGPT conversation and cannot open an existing ChatGPT Project conversation.

This is particularly frustrating because the interface already suggests that a split Chat/Codex workflow is supported, but the two systems remain isolated.

The side-panel selector should allow users to open:

• A new or existing normal ChatGPT conversation
• A conversation from a cloud ChatGPT Project
• A Codex task
• A Work conversation
• The built-in browser

6. Desired integrated workspace

The app should allow layouts such as:

• ChatGPT in the main pane
• Codex or the built-in browser in the right pane
• Terminal in the bottom panel

or the reverse:

• Codex in the main pane
• A normal ChatGPT Project conversation in the right pane
• Terminal in the bottom panel

Panels should be resizable, and the chosen layout should persist per project or window.

This would be much more useful than forcing ChatGPT and Codex into separate windows, because conversations, project context, browser content, and terminal output would stay organised in one workspace.

7. Normal ChatGPT needs direct local folder/file access

Please add direct local folder and file access to normal ChatGPT, equivalent to what Work and Codex can use.

Users should be able to attach or open a local project folder in an ordinary ChatGPT conversation and let ChatGPT inspect and work with those files without being forced into Work or Codex.

Work is not an adequate substitute for this because Work consumes the same usage allowance as Codex. Using Work solely to obtain local file access unnecessarily reduces the allowance available for actual Codex development work.

Expected outcome

The unified app should genuinely unify the tools rather than merely placing isolated modes inside the same shell:

1. Clearly identify every project and conversation as ChatGPT, Work, or Codex.
2. Apply distinct default icons/labels when the user has not customised them.
3. Keep conversation ordering and pinning consistent with the web app.
4. Make the side and bottom panels mode-independent.
5. Allow normal ChatGPT conversations to share a window with Codex, the browser, and the terminal.
6. Give normal ChatGPT controlled access to local folders and files.

Screenshots comparing the Windows app and web project views are available and can be provided if needed.