The unified ChatGPT app needs shared project state between Work and Codex

Codex
1

I think the new unified ChatGPT app exposes an important architectural gap between Work and Codex.

The problem is not that Work and Codex have different capabilities. Specialization makes sense.

The problem is that the user is effectively asked to manage the boundary between them.

My real-world use case is a medical review manuscript managed as a repository-driven project. The project has a structured phase system, audit artifacts, validation scripts, Git history, commits, and tagged checkpoints.

A typical task may involve:

  1. reviewing journal requirements;

  2. evaluating the scientific and medical narrative;

  3. inspecting multiple manuscript and audit files;

  4. modifying the manuscript;

  5. running consistency or citation audits;

  6. reviewing the Git diff;

  7. discovering a scientific wording problem;

  8. reconsidering the evidence or argument;

  9. revising the manuscript again;

  10. validating and creating a Git checkpoint.

This is one workflow.

It is not a “Work task” followed by a separate “Codex task.”

Research, reasoning, document production, repository operations, validation, and Git are interleaved within the same project trajectory.

In the current product model, switching between Work and Codex appears to create a context and state boundary. I cannot simply assume that Work has inherited the active Codex task state—including the current phase, previous decisions, rejected alternatives, constraints, and execution history—and vice versa.

As a result, the user has to reconstruct context or build a manual handoff protocol.

I think this is the wrong abstraction layer.

The user should manage a project and its objective, not decide which internal agent should own each step.

A project should own a shared structured state:

  • current objective and milestone;

  • completed work;

  • important decisions and rationale;

  • rejected alternatives;

  • active constraints;

  • unresolved issues;

  • execution and validation history.

Work and Codex should operate on that same project state.

The ideal architecture, in my view, is:

Project owns state. Agents perform work. Capabilities are tools.

The user stays inside the project and states the goal. ChatGPT dynamically uses research, connected apps, document, repository, terminal, Git, and review capabilities as required.

Advanced users could still explicitly choose a Work-focused or Codex-focused mode when needed, but the default should be an automatic project agent with capability routing.

Switching from Work to Codex should change the execution harness—not fragment the project’s working memory.

This matters especially for professional knowledge-engineering workflows: scientific research, quantitative analysis, technical writing, regulatory work, and other projects where domain reasoning and repository-based execution are tightly coupled.

The new unified app has brought Work and Codex into the same interface. The next step, I believe, is to give them a genuinely shared project-state layer.