Codex Desktop macOS: read_thread_terminal cannot see a working integrated terminal

Summary

In Codex Desktop on macOS, the integrated terminal is open and fully functional, but the agent-side read_thread_terminal tool cannot read it and always returns:

No app terminal session is attached to this thread yet.

The desktop logs show that the visible route uses the permanent thread ID while panel/session ownership continues to use a temporary client-new-thread:... ID. This appears to prevent the terminal snapshot lookup from finding the current thread's terminal.

Environment

• Codex Desktop: 26.623.141536 (build 4753)
• Bundled Codex CLI: 0.142.5
• macOS: 26.5.1 (25F80)
• Architecture: Apple Silicon (arm64)
• Authentication: ChatGPT
• Thread type: local/projectless desktop thread

Actual behavior

1. The integrated terminal opens inside the Codex app.
2. Commands run normally. codex doctor --all reports that stdin, stdout, and stderr are TTYs, with TERM=xterm-256color, and correctly identifies the current project.
3. Asking the agent to inspect the current terminal invokes read_thread_terminal.
4. The tool responds that no app terminal session is attached.
5. The same failure occurs with a second terminal tab.

Relevant sanitized desktop-log pattern:

conversationId=client-new-thread:<temporary-id>
ownerRoutePath=/local/<permanent-thread-id>

The IDs remain different after switching to another chat and returning.

Expected behavior

The terminal session visible in the current thread should be associated with the permanent thread ID, and read_thread_terminal should return the active integrated-terminal snapshot.

This is also the behavior described in the Codex app documentation: Codex can read the current integrated-terminal output.

Steps to reproduce

1. Open Codex Desktop on macOS.
2. Create a new local/projectless thread.
3. Open the integrated terminal in that thread.
4. Run:

``sh
printf 'codex-terminal-check\n'
``

1. Ask the agent to read/check the built-in terminal.
2. Observe:

``text
No app terminal session is attached to this thread yet.
``

Recovery attempts

• Closed and reopened the terminal panel.
• Created another terminal tab and selected it.
• Switched to another chat and returned.
• Quit and restarted Codex, then created a fresh terminal.
• Confirmed the Codex installation, databases, configuration, authentication, network, and thread inventory pass codex doctor --all.

The issue persists.

Additional information

No raw logs or full thread identifiers are included here because they can contain private information. A sanitized log excerpt or an in-product /feedback session can be provided if needed.