Feature Request: Live Context Inheritance Between ChatGPT Projects

ChatGPT Feature requests
, , , ,
1

Summary

Allow one ChatGPT Project to use another Project as a live context source, instead of requiring static file imports or manual copy-pasting.

For example, I may spend weeks building strategy, brand voice, frameworks, decisions, and project rules inside Project A, then create Project B for a specialized purpose such as content writing, analysis, or execution.

Project B should be able to inherit the relevant context from Project A and continue receiving updates as Project A evolves.

Why this matters

Right now, related Projects quickly become disconnected.

The available workarounds all have limitations:

  • Copy-pasting conversations is slow and difficult to maintain.

  • Re-uploading files only transfers a snapshot.

  • External tools like Google Docs or Notion usually capture final decisions, but not the conversational context, alternatives considered, trade-offs, or rationale behind them.

  • Once context is copied into multiple Projects, each copy can become outdated and version control becomes a problem.

The result is that users often have to re-explain the same background repeatedly.

Proposed Solution

1. Foundation Project

Allow a user to select another Project as a Foundation Project or Context Source.

Example:

Professional Brand

  • LinkedIn Content

  • Portfolio

  • Job Applications

  • Personal Website

The Professional Brand Project could act as the single source of truth while the other Projects remain specialized.

2. Live Context Link

The linked Project should be able to reference:

  • project instructions

  • files

  • important conversation context

  • decisions and recorded rationale

  • future updates to the Foundation Project

This should behave like a reference rather than a one-time copy.

3. User-Controlled Inheritance

Users could choose what gets inherited, for example:

  • Inherit instructions

  • Inherit files

  • Inherit project memory/context

  • Follow future updates

The relationship could be one-way by default:

Foundation Project → Linked Project

That would allow specialized Projects to use shared context without accidentally changing the Foundation.

Impact

This would be useful for:

  • creators managing brand strategy and content Projects

  • consultants handling multiple related client workflows

  • teams sharing research, SOPs, or company knowledge

  • product and research work

  • long-term writing and worldbuilding

  • anyone using ChatGPT for complex, evolving work

Instead of maintaining several disconnected copies of the same context, users could maintain one evolving source of truth feeding multiple specialized Projects.

That would make Projects feel much more like a connected workspace rather than isolated containers.

3

This is essentially a missing “context dependency” layer between Projects.

I’d model it more like a read-only dependency graph than copying context:

Foundation Project → Linked Project → Task/Chat

The important part is that the linked Project should resolve the Foundation’s current state at inference time, rather than materializing a snapshot.

That also makes versioning much cleaner: the user could see something like:

Source: Professional Brand v42
Inherited: instructions + selected files + decisions
Last synced: current

Then specialized Projects can consume the source of truth without becoming another source of truth themselves.

The one-way default is especially important — otherwise you quickly get circular dependencies and conflicting instructions.

4

The one-way default is the part I’d push for too. One thing worth adding: let the linked Project pick which parts it inherits (instructions and decisions, say, but not every file), otherwise a large Foundation quietly eats the context budget of every child. Until something like this exists, a short source-of-truth doc kept in the Foundation and attached at the top of each linked chat gets you most of the way. Put a version line at the top so you can tell when it’s stale.