›_ Codex Issues
Codex Issues / #40338

[Bug] Codex Desktop's built-in terminal cannot attach to the current chat and continuously returns queued

Open 💬 3 comments Opened Aug 24, 2026 by MarvinSunnnn
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

问题

在 Codex Desktop 的本地 Codex 任务中，内置终端无法创建并附着到当前聊天。结果是聊天无法读取终端输出，也无法向 UI 内置终端输入命令。

环境

  • ChatGPT Desktop / Codex：26.818.41509（build 6962）
  • macOS：15.7.9
  • 任务类型：本地 Codex 任务

复现步骤

  1. 打开一个本地 Codex 任务。
  2. 在该任务中请求打开内置终端。
  3. 读取当前聊天绑定的终端状态。
  4. 完整退出并重启 ChatGPT Desktop 后，在同一任务再次执行步骤 2 和 3。

实际结果

  • 打开终端请求持续返回：status = queued。
  • 读取终端持续返回：No app terminal session is attached to this thread yet.
  • 重启 Desktop App 后仍可稳定复现。
  • 请求发生时当前任务窗口已可见且获得焦点；当前聊天仍没有附着终端会话。

预期结果

当前本地 Codex 任务应创建并附着内置终端。聊天应能读取终端提示符和输出，并可在该 UI 终端中执行命令。

影响

内置终端在当前聊天中不可用。任务只能改用 Agent 的后台执行环境，用户无法在 UI 内置终端中查看、输入或让聊天读取实际命令内容。

补充

本次验证没有用后台终端的执行结果代替 UI 内置终端。若维护者需要，我可以通过安全渠道提供脱敏后的本地诊断日志。

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 4 days ago

English translation:

Issue

In a local Codex task in Codex Desktop, the built-in terminal cannot be created and attached to the current chat. As a result, the chat cannot read terminal output or enter commands in the UI's built-in terminal.

Environment

  • ChatGPT Desktop / Codex: 26.818.41509 (build 6962)
  • macOS: 15.7.9
  • Task type: Local Codex task

Steps to reproduce

  1. Open a local Codex task.
  2. In that task, request that the built-in terminal be opened.
  3. Read the status of the terminal associated with the current chat.
  4. Fully quit and restart ChatGPT Desktop, then repeat steps 2 and 3 in the same task.

Actual result

  • Requests to open the terminal continuously return: status = queued.
  • Reading the terminal continuously returns: No app terminal session is attached to this thread yet.
  • The issue remains consistently reproducible after restarting the Desktop App.
  • When the request is made, the current task window is visible and focused; no terminal session is attached to the current chat.

Expected result

The current local Codex task should create and attach the built-in terminal. The chat should be able to read the terminal prompt and output and execute commands in that UI terminal.

Impact

The built-in terminal is unavailable in the current chat. The task can only use the Agent's background execution environment, and the user cannot view or enter the actual commands in the UI's built-in terminal or have the chat read them.

Additional information

This verification did not use results from the background terminal as a substitute for the UI's built-in terminal. If the maintainers need them, I can provide redacted local diagnostic logs through a secure channel.

<!-- codex-issue-translator -->

github-actions[bot] contributor · 4 days ago

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

  • #39052

Powered by Codex Action

lange-donnern-bot · 21 minutes ago

Confirmed on Windows as a related attachment-path failure.

In this reproduction, read_thread_terminal can successfully read a manually opened integrated terminal in the current visible task. The agent then creates a separate interactive PowerShell PTY, writes test output successfully, and calls open_in_codex with that active sessionId and bottom placement.

open_in_codex returns status: queued, but the PTY is never displayed or attached. A subsequent read_thread_terminal call still returns the original manually opened terminal without the test output.

This suggests the queued terminal-attachment/delivery path can fail even when terminal snapshot lookup for the current task works correctly. It may be related to #39914, which reports the same indefinite open_in_codex queued state on Windows for another panel target.

No local paths, thread IDs, session IDs, or raw terminal logs are included.