Codex App could not read terminal

Same here. Hope they can fix. the integrated terminals have been mostly usless for me with CODEX since release.

+1

Same here for 26.616.41845 on Mac, it did work before update

I can reproduce the same issue on macOS.

Environment:

• Codex App: 26.616.71553 (4265)
• Bundle identifier: com.openai.codex
• Bundled Codex CLI reported by codex doctor: 0.142.0-alpha.6
• macOS: 26.5.1
• Shell: zsh
• Feedback ID: 019ee713-bb74-7f93-8ecc-df8b845fa6f8

Observed behavior:
The integrated terminal can be opened in the Codex Desktop UI, but the agent cannot read it. When the agent checks the terminal, it consistently receives:

No app terminal session is attached to this thread yet.

please fix it。
Code App: 26.623.31921

No app terminal session is attached to this thread yet.

Version 26.623.81905 • Released Jul 1, 2026
macos
same problem

This issue is still reproducible on Windows Codex App 26.630.12135. codex_app.read_thread_terminal still returns No app terminal session is attached to this thread yet.

Finally! It's now fixed at 26.721.30844, Released Jul 24, 2026! 💯

Still reproducible for me after the claimed fix.

Environment:

• ChatGPT/Codex App: 26.721.31836 (5828)
• Codex Doctor: 0.146.0-alpha.3.1
• macOS: 26.5.2
• Shell: zsh
• Feedback ID: 019ee713-bb74-7f93-8ecc-df8b845fa6f8

This happens even though the app version is newer than 26.721.30844, which was reported as fixed in this issue:
Observed:
codex_app.read_thread_terminal still returns:

No app terminal session is attached to this thread yet.

I can reproduce the same issue on macOS.

Environment:

• macOS 26.5.2 (Build 25F84)
• Apple Silicon (arm64)
• ChatGPT/Codex Desktop 26.803.81509

The integrated terminal is visible and fully interactive. For example, I can run:

% echo TEST
TEST

However, when the agent calls codex_app.read_thread_terminal, it consistently returns:

No app terminal session is attached to this thread yet.

The terminal shown in the UI therefore appears not to be attached to the current thread from the agent/tooling perspective.

I have reproduced this after:

• Restarting the app
• Completely removing and reinstalling the app
• Closing and reopening the terminal panel
• Closing existing terminal tabs and creating a new terminal from the current thread
• Creating and attaching a new shell session

The terminal remains usable by me, but the agent cannot read its output.

This suggests that the issue is not Windows-specific and may be a cross-platform problem in the Desktop app’s terminal-to-thread/app-server attachment layer. I can provide logs, a screenshot, and the affected thread ID if helpful.

Still reproducible on Windows:

• Codex Desktop 26.810.7004.0, x64
• Codex CLI 0.147.0
• Windows 11 10.0.26200

The integrated terminal is visible and interactive, but read_thread_terminal returns:

No app terminal session is attached to this thread yet.

The error appears 35 times in my local logs. Sanitized entries show:

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

This matches the thread ID mismatch in #31417. Microsoft Store currently offers no newer package.

Update: The integrated terminal is now readable in my local Desktop thread.

Previously, codex_app.read_thread_terminal consistently returned:

No app terminal session is attached to this thread yet.
After installing the latest app update, restarting the app, and setting a profile/avatar image, the terminal attachment started working. The tool now returns the integrated terminal snapshot correctly, including the working directory, shell, command, and output.
Example:
cwd: <local-project-path>
shell: zsh

% echo test
test

I cannot confirm which step actually resolved the issue. However, another user also mentioned that setting an avatar/profile image appeared to make the terminal work for them. This may indicate that a profile/account state refresh causes the Desktop app to re-materialize or repair the thread-to-terminal attachment state.
If others are still affected, it may be worth trying the following sequence:
Install the latest Desktop app update.
Fully restart the app.
Set or update the account profile/avatar image.
Open a new local Desktop thread.
Open the integrated terminal and run a simple command.
Ask the agent to read the terminal output again.
This does not prove that the avatar itself is the root cause, but it may be a useful workaround or diagnostic signal for stale account/session/thread metadata.

Additional Windows reproduction

Codex App version: 26.810.7004.0
Platform: Microsoft Windows NT 10.0.19045.0 x64

Actual behavior

After updating the Windows app on 2026-08-17, a newly opened integrated terminal in the currently visible thread is interactive and displays command output, but the agent cannot read it. codex_app.read_thread_terminal consistently returns:

No app terminal session is attached to this thread yet.

This functionality worked before the app update.

Steps to reproduce

1. Open a project thread in the Windows desktop app.
2. Open a new integrated terminal from the terminal button in the current thread.
3. Run a command and confirm that its output is visible and the terminal remains interactive.
4. Ask Codex to read the current thread terminal.
5. Observe the error above.
6. As an additional check, ask the current thread to open a terminal programmatically. The request is incorrectly returned as status: queued even though the thread is visible. Navigating back to the same thread and retrying still does not attach the terminal.

Expected behavior

Codex should be able to read the output of a newly created integrated terminal scoped to the currently visible thread.

totally same issue n bother me a lot.

totally same issue n bother me a lot.

Try choosing an Avatar!

Powered by Codex & OWL
版本 26.820.71523

发布于 2026年8月27日

什么辣鸡软件啊

I kept running into this and what i found out finally from Codex itself is that it could run this from a symlink'd directory. The project folder must be in a real live path that doesnt have a symlink in it.