Unified desktop app: Chat cannot reference Work tasks in the same Project

No repository files, tests, or entry points are named; first determine whether unified desktop Project, Chat, and Work integration exists in this repository. Done would require an agreed, permission-aware cross-surface reference design or documented clarification of the current behavior and Continue in Chat transfer scope.

Summary

In the unified ChatGPT desktop app, Chat and Work can appear inside the same ChatGPT Project while still using separate task and conversation context.

A new Chat created through Continue in Chat remains correctly associated with the same Project. However, that Chat cannot list, reference, or access the other Work tasks associated with the Project.

This is not a missing-task or lost-project-selection problem. The Work tasks remain available in Work, and the Chat remains in the correct Project. The problem is that the shared Project UI does not provide shared task visibility or a reliable cross-surface reference mechanism.

Environment

• ChatGPT desktop app: 26.715.31251
• macOS 26.5.2
• Apple silicon

Steps to reproduce

1. Open an existing ChatGPT Project in the unified desktop app.
2. Create or use multiple Work tasks associated with that Project.
3. From one Work task, choose Continue in Chat, or switch to Chat within the same Project.
4. Confirm that the new Chat remains assigned to the same Project.
5. Try to view or reference the other Work tasks from Chat.

Actual behavior

• The Chat stays inside the correct Project.
• Existing Work tasks remain visible in Work.
• Chat cannot discover, list, mention, or reference those Work tasks.
• The user must manually copy or summarize context between the two surfaces.
• A matching Project name implies more continuity than the product actually provides.

Expected behavior

At minimum, Chat should provide a project-scoped way to reference a Work task, such as a task picker or reliable @ reference.

Ideally, the Project should own a shared, permission-aware context layer containing:

• task titles and status;
• explicit handoff summaries;
• decisions and active constraints;
• user-selected artifacts or attachments;
• clear provenance showing which context came from Chat and which came from Work.

This should not silently grant Chat access to local files or execution capabilities. Any transfer of local artifacts or sensitive context should remain explicit and permission-controlled.

If full cross-surface access is not intended, the UI should clearly state that Chat and Work share only Project organization—not task history or working context—and explain exactly what Continue in Chat transfers.

Why this is distinct from related reports

• #33723 reports losing the cloud Project association when switching to Chat. Here, the Project association is preserved.
• #32130 requests broad unification and full Project access. This report focuses specifically on same-Project task visibility between Chat and Work.
• #33716 describes the mixed organization models.
• #31862 covers broader unified-desktop regressions.

Related OpenAI Community discussions

• Chat references of Codex inside ChatGPT
• [macOS] Web Project hierarchy missing in the desktop app, while hidden Work chats remain partially discoverable via @
• The unified ChatGPT app needs shared project state between Work and Codex

Requested clarification

Please document:

1. Whether same-Project Chat and Work tasks are intended to share any context.
2. Exactly what Continue in Chat transfers.
3. Whether Chat will gain a supported way to reference Work tasks.
4. Whether the current separation is temporary migration behavior or the intended architecture.