Feature Request: Unified History with Dynamic “Local Workload Migration”
Summary:
Allow Work Local chat history to sync across the cloud so context is never lost across devices, while treating the local hardware connection as a dynamic workload that can be remotely triggered or migrated.
The Problem:
Currently, choosing Work Local isolates the entire conversation history to a single machine. If I start a project at home and go to the office, my conversational context is left behind. While I understand this prevents conflicts (e.g., the AI not knowing whether to “remote control” the original machine or look for files on the new device), completely hiding the text history destroys the multi-device workflow.
Proposed Solution / Feature Request:
- Unified History Sidebar: All chat threads (both Cloud and Local) should be synced and visible across all logged-in devices.
- Context Preservation: I should be able to read my
Work Localchat history on my phone or office PC, even if that device doesn’t have the original local files. - Dynamic Workload Execution: When opening a
Work Localthread on a new device, instead of blocking the chat, give the user a clear toggle with two options:- Remote Execution: Trigger the tool/code workload back on the original host machine (if it is online/awake).
- Migrate Workload: Transfer the execution context to the current device, scanning the current machine’s local directories or programs instead.
Why this matters:
This bridges the gap between enterprise security/local execution and the seamless cross-device handoff that makes ChatGPT great. It stops users from accidentally trapping their context on the wrong computer.