Codex CLI session appears in ChatGPT Work instead of Codex history
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by reproducing the session-routing behavior with Codex CLI 0.144.5 and the reported ChatGPT desktop build, then inspect this repository for the CLI-to-desktop history integration entry points. Confirm whether the repository contains the affected desktop integration; done means CLI sessions consistently appear in Codex history rather than ChatGPT/Work, with regression coverage if an existing test area is found.
Written by the indexing model from the issue text.
Description
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?
- Start a task using Codex CLI in Terminal.
- Allow Codex CLI to complete a task that creates or modifies files.
- Open the ChatGPT/Codex desktop app.
- Check the ChatGPT/Work section.
- The Codex CLI session appears there with outputs.
- Open the Codex section.
- 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
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
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.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·