Repository navigation
[Dots][macOS → Mobile Remote] Dot-created Mac tasks are missing from the task list even after pinning #49848
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Codex Desktop 26.928.21956 (build 12404), verified from the installed application's Info.plist on October 1, 2026.
Exact mobile app version was not captured.
What subscription do you have?
Not captured in this investigation. The reporting account has access to Dots.
What platform is your computer?
macOS on Apple Silicon. uname -mprs returned Darwin 27.0.0 arm64 arm.
Mobile: ChatGPT mobile app, Remote task list for this Mac.
What issue are you seeing?
Two tasks created by OpenAI Dots to execute on the connected Mac are visible and directly readable on desktop, but absent from the mobile Remote task list. Pinning does not restore mobile visibility.
The desktop task interfaces were checked directly. The mobile behavior and failed pinning workaround were confirmed by the user during the same investigation; no mobile network trace was captured.
| Check | Task A | Task B |
|---|---|---|
Desktop list_threads |
Visible in pinnedThreads | Visible in regular threads |
| Reported hostId | durable |
durable |
Direct read_thread |
Succeeds, with execution history | Succeeds, with execution history |
| Preview | Empty string | Empty string |
Corresponding row in this Mac's local state_5.sqlite |
Absent | Absent |
| Mobile Remote task list | User confirms absent | User confirms absent |
At least one task's initial turn contains a delegation-wrapped userMessage while its reported preview remains empty. These are running/previously executed tasks with history, rather than blank prewarmed sessions.
This prevents the user from opening and monitoring Dot-delegated work from the phone even though desktop can access the work.
What steps can reproduce the bug?
- Use a Dot to create a task that executes on the attached Mac.
- Let the task execute and produce output.
- Confirm it appears in desktop task listing and can be read directly with history.
- Open the connected Mac's task list in mobile Remote.
- Observe that the Dot-created task is absent.
- Pin the task on desktop and check mobile Remote again.
- Observe continued absence. In the investigated setup, desktop confirms a pinned entry.
Two existing tasks were checked; no new tasks or test messages were created for this report.
What is the expected behavior?
Dot-created tasks executing on the connected Mac should be discoverable and accessible from mobile Remote, including when pinned on desktop.
If these durable-backed tasks are intentionally outside the connected-host Remote list, please provide a supported mobile route and make that scope distinction clear in the UI.
Additional information
Related: #32614, with my earlier September 5 investigation.
This report is separate because the observed behavior differs:
- In the September 5 case, an affected task had a local state row, was absent from ordinary desktop discovery, and became visible on the connected iPhone after pinning.
- In this Dots case, desktop already lists both tasks, their hostId is
durable, neither has a corresponding local state row, and pinning still does not expose them on mobile.
#49482 concerns discovery of the supported route for a Dot to continue existing local Codex chats; that route succeeded in its reported test. This report concerns the mobile task list after a Dot has already created and executed a task.
No identical recent Dots/mobile task-list report was found in the searches performed. Please consolidate with #32614 if these variants share the same underlying issue.
The leading investigation area is mobile discovery of durable tasks associated with a Mac executor, including host/environment association and pinned-task resolution. Empty preview is a shared characteristic, but the same preview-filter root cause has not been established. Local database absence alone does not prove mobile's selection predicate.
Still missing: mobile build, mobile list request/response, and authoritative durable-task association with the connected Remote host. No claim of a confirmed root cause or fix is made.
No database, installed app, or settings changes were made. No private task IDs, titles, prompts, account identifiers, local paths, screenshots, or raw logs are included in this public report.
Activity
RCX1t7 commentedon Oct 2, 2026
I'm seeing a very similar issue with a Windows host, on both iPhone and iPad.
Dot-created tasks execute on my connected Windows computer, but they do not appear on either mobile device after I select that computer in Codex/Remote. This is not just looking for them in the main dot chat list.
The affected tasks exist and have execution history; they can be read through the task interface. I have not verified the local database or hostId details described in the original report, so I can't confirm that the underlying cause is identical. Exact desktop/mobile app build numbers have not been collected yet.
Please include Windows with iOS/iPadOS when investigating this task-discovery issue. Is there a supported way to open dot-created local-computer tasks from mobile in the meantime?
hayatokyo commentedon Oct 2, 2026
I can confirm the same behavior on another setup.
This makes it difficult to hand work from a Dot to Codex on the computer and then monitor/continue that same work from iPhone Remote.
Observed again on October 3, 2026 (Japan time). I have not modified local databases or thread metadata. Happy to provide sanitized thread metadata, app versions, or diagnostics if maintainers specify what would be useful.
jeanefpraxiadis-jpg commentedon Oct 2, 2026
I also see this on Windows and iPhone, both before and after updating both apps on October 2. Dot-created tasks run on my PC and are usable there, but are absent from iPhone Codex Remote. One older task is visible but cannot be opened or prompted. Reconnecting did not fix it. Is there a supported mobile route or a fix planned?
fukaya0404 commentedon Oct 4, 2026
Adding a same-Mac comparison observed on October 4, 2026:
hostId: durable. It is readable on the Mac, but I cannot find it in the iPhone Remote task list or search.create_threadAPI using its default local behavior.read_threadconfirmedhostId: local, and I personally confirmed that this new conversation was visible on my iPhone.This was one newly created comparison conversation, not a conversion of the existing durable conversation. It shows a visibility difference in this setup, but does not establish the root cause or guarantee that local conversations will always be visible. Current desktop and mobile app versions were not captured for this test.
Meowzz95 commentedon Oct 4, 2026
Same here I think this is because dot created threads are cloud thread
shivacyberpunk commentedon Oct 13, 2026
I am also seeing this on a connected Mac and iPhone as of October 13, 2026.
Observed sequence:
This affects all of my dot-delegated tasks in this setup. On desktop, the sidebar entry also disappears after every app restart and returns only when I reopen the task link; I added that observation to #51675.
I cannot find and monitor this delegated work from my phone. Exact desktop/mobile build numbers have not been verified for this report, and I have not established the root cause or tested pinning as a workaround.
Is there a supported mobile route for these existing tasks, or a confirmed fix?
mlchild commentedon Oct 14, 2026
Additional occurrence observed October 14, 2026, with a connected Mac mini and iPhone.
The user reports that a dot-created task executes on the selected Mac and is readable on desktop, but cannot be found in the iPhone's view of that same computer under Pinned, Projects, or Recents. An ordinary local task appears normally.
Read-only checks through the supported desktop thread tools confirmed:
kind: codex,hostId: durable, andprojectId: null; its desktop sidebar section is Tasks.kind: codexandhostId: local, belongs to a local project, and is pinned.The phone behavior is user-reported; no mobile network trace or direct mobile UI inspection was performed. Exact desktop/mobile build versions were not collected. Pinning or moving the affected task was not tested in this occurrence. The
durable/localdistinction is an observed correlation, not a diagnosed cause, and the exposed metadata does not independently establish how the affected task was created.Expected: tasks running on the same selected computer should have a clear, consistent way to discover, read, and continue them across desktop and mobile. If some task types intentionally live outside the connected-host list, please expose the supported route and explain the distinction in the UI. The current navigation is confusing even though the task and its results remain accessible on desktop.
No private task IDs, titles, conversation contents, local paths, account details, screenshots, or logs are included in this report.