[macOS / dots] Cannot read manually created Codex threads (placement format v2/v3); repeated app approvals #52247

Environment

• macOS desktop, with the computer connected and authorized for dot tasks
• ChatGPT Pro; dot used from the desktop app and Android
• Observed on October 8, 2026
• Exact desktop app build and macOS version were not captured. Please do not infer them from the linked reports.

1. dot cannot read manually created Codex conversations

I created local Codex conversations myself from project folders, then gave dot their codex://threads/... links and explicitly asked it to check progress. The conversations existed and could be used locally, but dot's direct thread-read route failed for two separate conversations:

AppServerBackendRequestError: Client specified an invalid argument:
post-cutover thread ID [redacted] has unsupported placement format version 2

AppServerBackendRequestError: Client specified an invalid argument:
post-cutover thread ID [redacted] has unsupported placement format version 3

Trying to send an instruction directly to the second conversation also returned:

CloudThreadNotFoundError: The cloud thread was not found.

A local executor's thread-read API could read that second conversation, while dot's direct route could not. This suggests a difference between the access paths; it does not establish the root cause. Creating an extra conversation just to relay messages is not a practical replacement for direct access to the original task.

Reproduction

1. Keep the Mac connected and authorized for dot tasks.
2. Manually create a Codex conversation inside a local project and use it normally.
3. Copy its conversation link to dot.
4. Ask dot to read its progress or continue that specific task.
5. The direct read fails with the placement-format error above; a send may report that the thread was not found.

Expected

After I identify and authorize access to an existing local task, dot should be able to read it, or explain a specific missing permission. I am not asking for automatic access to every conversation.

2. Repeated Computer Use approval in a dot-created task

In a separate dot-created inspection task, the Mac repeatedly showed a Computer Use prompt asking whether ChatGPT could use T3 Code Nightly. I selected Always allow several times, but the task continued waiting for approval.

The intended inspection target was later clarified as Ghostty. I understand that terminal-app automation has separate product restrictions; this report does not request bypassing them. The observed problem here is the repeated approval prompt for T3 Code Nightly despite selecting Always allow. I have not established whether this shares a cause with the thread-access errors.

Impact

I cannot reliably check work I started manually on my Mac through dot while away with only my phone. Repeated approvals also prevent unattended tasks from progressing.

Related reports

• Dot cannot read an existing local Work thread: unsupported placement format version 2 #50698 — placement format version 2
• Dot cannot connect to codex conversations Error unsupported placement format version 3 #51731 — placement format version 3
• Thread started by dot on mac codex loop on browser use approval #51720 — repeated app approval in a dot-created Mac task

This report adds our macOS reproduction and separates the two symptoms. Feel free to consolidate with those issues. Private thread IDs, project paths, account details, and conversation contents have been omitted.