Dot only created Cloud-labeled Codex tasks in my tests

In my tests, every task Dot successfully created was a Codex task labeled “Cloud.” I couldn’t get it to create a Work task, either locally or in the cloud, or confirm that it had created a native local Codex conversation in the Windows sidebar.

I tested on November 20, 2026 (UTC+8), from Dot’s main conversation in the ChatGPT iOS app. My Windows PC was connected to Dot with local access enabled. I made the requests in Chinese.

- **Local Work (11:01–11:03):** I asked Dot to create a Work task on my connected Windows PC. Dot said it couldn’t find a way to create one. It reported that no task was created and no test message was sent.

  • **Cloud Work:** I separately asked Dot to create a cloud Work task. Dot said it couldn’t find an option to create one. In a separate test at about 11:14, I asked for a generic cloud task, and it opened as Codex.
  • **Native local Codex (around 11:18):** I explicitly asked Dot to create a local Codex conversation on the same Windows PC. The test command ran on that PC, but the task composer on iOS still showed “Cloud,” as shown in the screenshot. I haven’t confirmed whether that conversation appeared in the native Codex sidebar on Windows.

I also tried continuing an existing Work conversation. Dot could find it but said it couldn’t send a follow-up message.

**Versions:** Windows 11 Pro (OS version 10.0.26300), ChatGPT desktop package 26.1111.9664.0, and ChatGPT for iOS v1.2026.307 (build 42345155361).

Which of these three creation paths are currently supported: native local Codex, local Work, and cloud Work? For the Windows Codex test, is it expected that a task running commands on the connected PC still shows “Cloud” on iOS? I’ve already contacted OpenAI Support, but I’d also like to know if anyone has reproduced this or found a workaround.

Reference: [Getting started with your dot](https://help.openai.com/en/articles/20001530-getting-started-with-your-dot)