Project Workspaces with Shared Context Across Related Chats

What variant of Codex are you using?

Codex APP | ChatGPT with Codex

What feature would you like to see?

I'd like to propose an optional **Project Workspace ****feature that allows users to group a small number of related chats or Codex sessions--perhaps 3-5--into a shared workspace.

Each chat would remain an independent conversation focused on a specific part of a larger project, while being able to access a controlled set of shared project context.

For example, a technical project could contain:

• Development Chat - application code, scripts, APIs, and debugging
• Networking Chat - network design, VLANs, routing, firewalls, infrastructure, and troubleshooting
• Documentation Chat - README files, technical documentation, diagrams, and procedures
• Planning Chat - requirements, architecture decisions, milestones, and project goals

The important distinction is that these chats would not be merged into one large conversation. Each would retain its own history and specialized focus.

Instead, they could share a project-level context containing information such as:

• Project goals and instructions
• Shared notes
• Uploaded files
• Technical requirements
• Architecture information
• Important decisions
• Environment details

Users should remain in control of what is shared. For example, information discovered in one chat could have an "Add to Project Context" option rather than automatically exposing the entire conversation history to every other chat.

A Development Chat could therefore learn an important networking decision from the shared project context without needing access to the Networking Chat's complete conversation history.

Conceptually:

Project Workspace
│
├── Shared Project Context
│ ├── Goals
│ ├── Instructions
│ ├── Notes
│ ├── Files
│ ├── Requirements
│ └── Important Decisions
│
├── Development Chat
├── Networking Chat
├── Documentation Chat
└── Planning Chat

Relevant workspace information could be retrieved when needed rather than injecting every conversation into every prompt.

This could reduce repetition, keep complex projects organized, prevent individual conversations from becoming extremely long, improve context relevance, and give users explicit control over what information is shared between related chats.

The core idea is:

Multiple focused conversations collaborating around a controlled set of shared project context while remaining independently organized.

Additional information

I searched the existing issues before submitting this proposal and found a couple of related requests, particularly #35197 and #37085.

I believe this proposal is related to, but distinct from, those requests.

#35197 focuses on unifying Chat, Work/Codex, Projects, and repository workflows into a single project workspace.
#37085 focuses on persistent, non-versioned project-level knowledge and context for Codex.
This proposal focuses specifically on allowing multiple independent, specialized chats or sessions within the same project to share a controlled project-level context without merging their conversation histories.

For example, a Development chat, Networking chat, Documentation chat, and Planning chat could remain separate while sharing selected project goals, files, notes, requirements, and decisions.

I think these ideas could potentially complement each other: a persistent project-context layer could provide the shared knowledge, while separate chats or sessions could consume relevant portions of that context based on their individual roles.

An important design goal would be user control. Rather than automatically sharing all conversation history, users could explicitly choose what becomes project-level knowledge and which chats are allowed to use it.