[Bug] Codex Desktop's built-in terminal cannot attach to the current chat and continuously returns queued
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
问题
在 Codex Desktop 的本地 Codex 任务中，内置终端无法创建并附着到当前聊天。结果是聊天无法读取终端输出，也无法向 UI 内置终端输入命令。
环境
- ChatGPT Desktop / Codex：26.818.41509（build 6962）
- macOS：15.7.9
- 任务类型：本地 Codex 任务
复现步骤
- 打开一个本地 Codex 任务。
- 在该任务中请求打开内置终端。
- 读取当前聊天绑定的终端状态。
- 完整退出并重启 ChatGPT Desktop 后，在同一任务再次执行步骤 2 和 3。
实际结果
- 打开终端请求持续返回：status = queued。
- 读取终端持续返回：No app terminal session is attached to this thread yet.
- 重启 Desktop App 后仍可稳定复现。
- 请求发生时当前任务窗口已可见且获得焦点；当前聊天仍没有附着终端会话。
预期结果
当前本地 Codex 任务应创建并附着内置终端。聊天应能读取终端提示符和输出，并可在该 UI 终端中执行命令。
影响
内置终端在当前聊天中不可用。任务只能改用 Agent 的后台执行环境，用户无法在 UI 内置终端中查看、输入或让聊天读取实际命令内容。
补充
本次验证没有用后台终端的执行结果代替 UI 内置终端。若维护者需要，我可以通过安全渠道提供脱敏后的本地诊断日志。
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the queued terminal request in a local Codex task on macOS, including after restarting the desktop app, and inspect the available diagnostic logs if they can be provided safely. The issue names no source files, entry points, or tests, so trace terminal-session creation and attachment for the current chat. Done means the built-in terminal attaches reliably, exposes its prompt and output to the chat, and accepts commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100