Projects should sync local work history across devices

I find the current behavior of Projects + Local Work extremely frustrating.

I created a Project specifically so that my chats, context, files, and work around a topic would remain organized in one persistent workspace.

However, I later discovered that Work conversations created locally inside that Project are not accessible from my other devices, even though I’m signed into the same ChatGPT account and the Project itself appears on those devices.

This breaks the mental model and usefulness of Projects.

A Project should be a persistent, cross-device container. Whether a Work task executes locally on my machine or in the cloud should be independent from whether I can access its conversation history.

Ideally the architecture should work like this:

• Project and conversation history → synced to the account/cloud
• Work execution environment → Local Mac or Cloud

If I open a Local Work conversation on another device, I should at minimum be able to read the entire conversation and continue discussing it. If an operation specifically requires my Mac, ChatGPT could simply indicate that the Mac needs to be connected.

There also needs to be a migration option for existing conversations:

“Convert Local Work to Cloud Work”
or
“Sync this conversation to Project”

I already have existing Local Work conversations containing substantial work and context. Manually creating summaries and rebuilding those conversations in Cloud Work is not a reasonable migration experience.

My expectation as a paying user is straightforward:

Same account + Same Project = access to my Project history across my devices.

Local execution should not mean local-only conversation history.

Please consider:

  1. Cross-device read access for Local Work conversations.

  2. Cloud synchronization of conversation history independent of execution environment.

  3. A Local Work → Cloud Work migration option.

  4. Clear indication before creating Local Work that the conversation will not appear normally on other devices.

  5. A unified Project history showing Chat, Cloud Work, and Local Work consistently across devices.

This limitation significantly reduces the value of Projects as a long-running workspace.

I raised a related continuity request with Support on August 24. In my existing Chat, “Continue in Work” offered only “On your computer”; using Cloud Work required a separate thread and a manual handoff.

A useful improvement would let users choose Local or Cloud when continuing an existing conversation, while preserving its history and Project context. Any local files or dependencies that cannot move should be identified before switching. That would make the migration explicit and avoid rebuilding the conversation from a summary.

The gotcha I’ve been battling with is Chat’s insistence to switch to work rather than stay in chat. That’s a one way street. I’ve had four major streams end up being locked to a single machine through that innocuous question. I’ve even had chat suggest switching to work saying it allows portability between machines (my main requirement).