Codex CLI session appears in ChatGPT Work instead of Codex history

Open 💬 0 comments Opened Jul 17, 2026 by ald8s

What version of the Codex App are you using (From “About Codex” dialog)?

26.715.21425

What subscription do you have?

ChatGPT Plus

What platform is your computer?

27.0.0 arm64 arm

What issue are you seeing?

A Codex CLI session is appearing in the ChatGPT desktop app under ChatGPT/Work instead of appearing in the Codex section.

I started the task using Codex CLI in Terminal. After completion, the session appeared as a ChatGPT Work thread and showed generated outputs (for example Work-Logs.md).

However, when opening the Codex section in the desktop app, it shows "No chats" and "No projects".

The session logs confirm this was created by Codex CLI:

  • originator: codex-tui
  • source: cli
  • thread_source: user
  • Codex CLI version: 0.144.5

Expected behavior:
Codex CLI sessions should appear in Codex history.

Actual behavior:
Codex CLI sessions appear under ChatGPT/Work while Codex history remains empty.

What steps can reproduce the bug?

  1. Start a task using Codex CLI in Terminal.
  2. Allow Codex CLI to complete a task that creates or modifies files.
  3. Open the ChatGPT/Codex desktop app.
  4. Check the ChatGPT/Work section.
  5. The Codex CLI session appears there with outputs.
  6. Open the Codex section.
  7. Codex shows "No chats" and "No projects".

I fully quit and relaunched the desktop app, but the issue remained.

Environment:

  • macOS 27 beta
  • ChatGPT desktop app build 26.715.21425
  • Codex CLI version 0.144.5
  • Same OpenAI account used in CLI, desktop app, and browser.

What is the expected behavior?

The expected behavior is that any session created through Codex CLI should appear in the Codex section/history of the desktop app, not under ChatGPT/Work.

The Codex desktop app should correctly recognize and display Codex CLI sessions associated with the same OpenAI account.

After running a task from Codex CLI, I should be able to find that session in Codex history and continue working from the Codex interface.

Additional information

_No response_

View original on GitHub ↗