OpenAI’s latest Help Center documentation confirms that local work sync connects a Work conversation started with local execution on desktop to a cloud-coordinated conversation that can be continued on web or mobile. Admins must enable both Local Work and Cloud Work for the intended members and then separately enable local work sync in Work permissions.
The capability applies only to new tasks created after sync is enabled. Existing local tasks, including tasks in projects, are not migrated. If the connected computer is offline when a new turn begins, that turn can start in a cloud container but cannot use files or tools from the unavailable computer. A turn already running locally does not automatically move to the cloud.
Synced tasks are coordinated in the cloud even when a step executes on a local computer, so local execution does not mean that conversation content, tool results, or task context stay only on that device. OpenAI states that local work sync can support applicable data residency, inference residency, and EKM configurations, but Zero Data Retention is not supported. Codex workflows and conversation history remain separate from this Work capability.
The same Help Center page also confirms that the admin surface for agent policies is moving from Policies & Config to Agent Security. Existing cloud policy becomes the Global baseline after migration, while supported Local and Codex Cloud environment settings can override parts of that baseline; otherwise they inherit the Global settings.
