Feature Request: GitHub-Tracked Project State Shared Across ChatGPT Projects and Codex

Codex
1

I’m running into a consistency problem when using both ChatGPT Projects and Codex on the same codebase.

My workflow is:

  1. I architect the project and use ChatGPT to generate implementation files.
  2. I use Codex to make changes, iterate, and refine the code in the real repo.
  3. The project then drifts because ChatGPT is still working from an older internal view of the codebase, while Codex is working against the current version.
  4. The only actual source of truth is the GitHub repository, but ChatGPT does not stay synced to that truth automatically.

This creates a practical problem: ChatGPT may generate code for one version of the project, while Codex is modifying another. Over time, this causes conflicting assumptions, duplicated work, stale edits, and architectural drift.

Requested Feature

Add a shared GitHub-backed project state for both ChatGPT Projects and Codex, so both tools can reference the same current repository state.

What would help

  • Ability to connect a ChatGPT Project directly to a GitHub repository or branch.
  • Automatic awareness of the latest commit, branch, PR, or working tree state.
  • A visible “source of truth” indicator showing what revision the assistant is using.
  • Sync between ChatGPT and Codex so both operate from the same project snapshot.
  • Warning when generated code is based on stale repo state.
  • Option to pin a conversation/session to a specific commit, branch, or PR.
  • Easy refresh/update action when GitHub changes.
  • Shared project memory derived from the repo, not just from prior chat context.

Ideal Workflow

  • I attach a GitHub repo to a ChatGPT Project.
  • Codex and ChatGPT both read from that same linked project state.
  • If Codex changes the repo or a PR is merged, ChatGPT sees the updated state.
  • When ChatGPT generates new code, it does so against the latest known repo version.
  • If there is drift, the system explicitly says: “Your current conversation is based on commit X, but GitHub is now at commit Y.”

Why this matters

For real development workflows, chat context is not a reliable source of truth. GitHub is. If ChatGPT Projects and Codex do not share repo-aware state, they naturally diverge, especially on longer projects. A GitHub-tracked shared context would make both tools much more reliable for ongoing software development.

In short

Please add first-class GitHub state tracking and synchronisation across ChatGPT Projects and Codex, so both tools can stay aligned to the same live codebase instead of drifting into separate versions of the project.