Inserting the ChatGPT conversation into Codex will cause Codex to crash.

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #32190
• #30914
• #31020

Powered by Codex Action

I was about to report this yesterday but ended up doing a little bit of testing to be more precise about what's going on.

Codex itself was used to capture relevant logs (chatgpt-task-hang-feedback-upload-20260711-173645.zip).

The whole thing is reproducible on my end by referencing a server-backed conversation (@name-of-chat) + a long prompt.
The task will then end up poisoned (cant click on it on desktop app anymore because it will hang the app)

Here is the report I was going to send.

---

Pressing Send on a 7,247-character prompt (used audio-to-text) combined with a server-backed ChatGPT conversation reference freezes the Windows desktop renderer. The app frame remains responsive enough to minimize or close, but the task UI cannot be clicked and the pointer stays in its last state. Windows never reports the whole app as hung.

After a manual restart, clicking the affected task freezes the renderer again. The task is then always inaccessible from Windows desktop, even though it still accessible from mobile, and not visible in the ChatGPT web conversation list (not sure if this is expected).

One affected Codex task/thread ID: 019f531c-3ce5-7a03-972a-b862b86631a8

Trigger

• Exact prompt: attached as poison-trigger-prompt.txt (7,247 Unicode characters / 1,376 words / 7,249 UTF-8 bytes)
• Referenced conversation name: Brain Architecture Design (seen as a chat in my openai account, even though it was generated by selecting some text and clicking "more details" in the new menu)
• Failure begins when Send is pressed/clicked
• Observed without recovery for more than five minutes

Controls

• The long prompt works by itself.
• The same referenced conversation works by itself with a short prompt and attaches its full context.
• Two fresh server-backed references work with short prompts.
• Local side chats, normal local tasks, and project tasks can be referenced successfully.

⚠️ The confirmed failure requires the long prompt and large server-backed conversation reference together.

Persistent effect

After the failed send:

1. The desktop renderer freezes.
2. The app is closed manually using the still-responsive native frame + selecting "Quit" from taskbar icon.
3. After restart, the task remains in the task view.
4. Clicking it freezes the renderer again.
5. The task remains accessible on mobile but not Windows desktop.

A/B isolation

I performed the following tests to rule out independed issues:

| Input/action | Result |
| --- | --- |
| Exact prompt without reference | ✅ Works |
| Brain Architecture Design reference with short text |✅ Works and imports full context |
| Two new server-backed references with short text |✅ Work |
| Local side-chat reference |✅ Works |
| Normal local Codex task reference |✅ Works |
| Project task reference |✅ Works |
| Exact prompt plus Brain Architecture Design reference | ⚠️ Renderer freezes and task becomes inaccessible |

Cross-client state

• Windows desktop: task remains listed; opening it freezes the renderer.
• Mobile: the same task remains accessible, including after repeated failed desktop-open attempts.
• ChatGPT web conversation list: the chat cannot be found.
• Mobile OS/app version and a mobile screenshot were not available during evidence packaging.

Expected behavior

The request should submit, or the app should reject it with a recoverable payload/context error. A failed submission must not persist a task state that freezes the renderer whenever the task is reopened.

Environment

• App package: OpenAI.Codex_26.707.3748.0_x64__2p2nqsd0c76g0
• Desktop internal release in logs: 26.707.31428
• Chromium/file version: 150.0.7871.101
• Codex CLI from task metadata: 0.144.0-alpha.4
• Bundled Node/npm: 24.14.0 / 11.9.0
• Windows Pro 25H2, build 26200.7623, x64
• NVIDIA GeForce GTX 1050 Ti, driver 32.0.15.6094
• Timezone: America/Halifax (UTC-04:00)

The issue remained reproducible after closing the app, renaming the previous AppData/cache folders, rebooting, and reinstalling.

Logs

Note: some details on this log make reference to some earlier errors I was tracking related to a in-app-browser related crashes that i was experiencing before this major bug showed up.

Desktop logs show successful thread/read, thread/resume, and turn/start for the affected task, followed by repeated renderer ResizeObserver loop completed with undelivered notifications errors. Manual shutdown later produces route-window-not-live and EPIPE messages. These are correlated evidence, not a proven root cause.

Newer package-scoped logs also show that earlier bundled_executable_relocation_failed warnings did recur later, contrary to the initial capture. The app server still connected and accepted the turn, so whether those warnings contribute is unknown.

No aligned Windows AppHang, Application Error, WER crash, GPU/display failure, or WHEA event was captured.

Independent Windows reproduction of the same "poisoned task" failure, reported here because the affected task cannot be opened to use in-app feedback.

Environment

• Unified ChatGPT/Codex Windows app package: OpenAI.Codex_26.707.9981.0_x64__2p2nqsd0c76g0
• Windows 25H2, build 26200.8655, x64
• Date observed: 2026-07-13 to 2026-07-14

User-visible behavior

1. Start from an existing pinned/server-backed ChatGPT conversation.
2. Use Add to task in the new unified Windows app.
3. The resulting task becomes inaccessible/broken.
4. Reopening the affected task does not recover it, so /feedback cannot be invoked from that task.
5. The user also loses reliable access to the original pinned conversation in the new app.

This appears consistent with the Windows "poisoned task" reproduction already described above, but the local logs provide an additional asset-import failure signature.

Sanitized local log evidence

Across the recent app logs:

• 450 occurrences of ChatGPT conversation image download request failed
• 1,347 related Invalid file_id, expected to start with 'file-' or 'file_' entries
• The corresponding /files/download/{file_id} requests return HTTP 422
• 16 Received turn/started or turn/completed for unknown conversation errors
• 7 Item not found in turn state errors
• A chatgpt-conversation:// import reference appears immediately before the affected task state is created

The malformed imported assets have a pointer shape equivalent to:

sediment://<legacy-hash>#file_<redacted>#p_<redacted>.jpg

The desktop app then appears to send <legacy-hash> as the download file_id, which the server rejects because it does not begin with file- or file_. After these failures, the renderer/app state reports unknown conversations and missing turn items.

No conversation names, contents, account IDs, conversation IDs, task IDs, file hashes, or attachments are included here.

Expected behavior

Add to task should either import the ChatGPT conversation and its assets successfully or fail recoverably. A malformed legacy asset reference must not create a persistent task that becomes inaccessible, and the original pinned conversation should remain available.