Unify Chat, Work, Projects, and repositories into a single project workspace #35197

What variant of Codex are you using?

App on MacOS, also CodexCLI in Terminal.

What feature would you like to see?

Unify Chat, Work, Projects, and repositories into a single project workspace

I’ve been using ChatGPT and Codex extensively on a long-running software and research project.

The current architecture separates:

•	Chat conversations
•	Work/Codex tasks
•	ChatGPT Projects 
•	Repository context

Although each component is individually useful, they do not function as a coherent project workspace.

Current workflow:

1	Discuss implementation in Chat.
2	Chat produces a prompt.
3	Manually paste the prompt into Work (or Codex/Codex CLI)
4	Work executes.
5	Copy Work output back into Chat.
6	Chat reviews.
7	Repeat.

There are variations on the above theme such as:

1. Discuss open issues and discover need for new primary source research on some element of the project in chat.
2. Chat produces a Research Prompt for Deep Research.
3. Manually paste that into a new thread and /deepresearch.
4. Manually upload the output to the main thread in the project.
5. Chat identifies changes needed in the project and writes a prompt for Work (or Codex) to update the code or documentation.
6. Manually paste the Work/Codex output back to Chat and continue discussion, next steps for project
7. Repeat.

This creates unnecessary friction because Chat and Work already exist within the same application.

Instead, I believe the primary abstraction should be a Project, containing:

•	repository
•	uploaded documents
•	project instructions
•	conversation history
•	long-running memory
•	active Work tasks
•	research artifacts
•	decision log
•	TODOs

Within that project:

•	Chat should be able to launch Work tasks directly.
•	Work results should automatically appear in the project conversation.
•	Chat should be able to review Work output without copy/paste.
•	Both Chat and Work should share the same instructions and repository context.

The distinction between “thinking” and “modifying the repository” should remain explicit—the user should approve implementation—but the handoff between Chat and Work should be seamless.

The current architecture feels like coordinating multiple separate applications.

The underlying capabilities already exist; the missing piece is a unified project model. The project—not the conversation or the agent—should be the primary unit of organization. Conversations, Work tasks, research jobs, automations, repositories, and shared instructions are all facets of the same project and should operate over the same persistent context.

Note: I would be happy to discuss this further and share more context if helpful. I realize there are many possible workflows using these tools, but I don't understand how I could modify my workflow to improve it with the current tools to eliminate the considerable friction I face.

Additional information

No response