[Windows desktop] "Add to task" reference leaves task stuck while VS Code completes
Open 💬 1 comment Opened Jul 14, 2026 by Anz142431
Summary
On the Windows Codex desktop app, adding an existing chat/task to a new Codex task using Add to task causes the task UI to remain stuck after sending. The same task completes normally in the VS Code extension.
Environment
- Codex desktop app for Windows:
26.707.9564.0(x64) - Windows 11, build
26200 - VS Code extension:
openai.chatgpt-26.707.41301(works normally)
Steps to reproduce
- In the Windows desktop app, create a new local Codex task.
- Use Add to task to attach an existing ChatGPT chat or Codex task. It appears in the composer as a blue reference chip (for example,
项目基线更新). - Send a prompt that refers to the attached context.
Expected behavior
The desktop task completes and renders the response, matching the VS Code extension.
Actual behavior
- The desktop app remains in a processing/loading state and does not render the completed response.
- The same prompt/task has already completed and its full response is visible in the VS Code extension.
- Reopening an affected task (and continuation tasks that reference it) can leave the desktop conversation pane blank or make the desktop client unresponsive.
- Restarting and updating the desktop app did not resolve the issue.
Impact / workaround
Avoiding Add to task and pasting a plain-text handoff summary works around the issue. Existing affected task data remains usable in the VS Code extension but is unsafe to open in the desktop app.
No repository paths, account identifiers, or screenshots are included here. I can provide a screenshot privately if needed.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗