What variant of Codex are you using?
App and CLI
What feature would you like to see?
I use both the Codex desktop app and the Codex CLI on the same Mac. When I start a new CLI conversation from a folder that already exists as a Codex app project, the desktop app notices the new chat immediately. The chat appears in the project sidebar with the first prompt. After that, the app does not appear to keep refreshing the externally updated thread: it does not show that the CLI turn is running, does not stream or otherwise indicate progress, and does not load the assistant response after the CLI finishes.
The requested feature is for the desktop app to live-refresh local sessions that are created or updated by standalone CLI processes.
Ideally:
- A CLI-created thread that appears in the app sidebar should show a running or progress state while the CLI turn is active.
- The chat history should show some kind of easily visible indicator or message like "Chat is running in CLI".
- When the CLI turn completes, the app should load the new assistant message without requiring an app restart.
- If live streaming from standalone CLI turns is not practical, the app should provide an explicit
Refresh thread or Reload project sessions action in both the conversation window (replace in the "chat is running in CLI"), and in the sidebar with either an "unread" indicator, or a new indicator specific for this new behavior. The refresh thread action should also be available from the chat context menu in the sidebar.
This would make the app and CLI work together as one coherent local workflow. Some work is easier to start from a terminal, while reviewing sessions and switching projects is often easier in the app. Since the app already detects the new CLI-created chat, it is surprising that the visible thread stays stale until the app is restarted.
Additional information
Observed behavior:
- Start the Codex desktop app.
- Open an existing local project in the app.
- In Terminal, start a CLI session from the same project folder, for example
codex --cd /path/to/project.
- Send the first prompt in the CLI.
- Watch the desktop app sidebar and the corresponding thread.
What happens today:
- The new chat appears in the app sidebar almost immediately, including the first prompt.
- The app does not show progress while the CLI is working.
- After the CLI finishes, the app still does not show the assistant response.
- Quitting and restarting the Codex app causes the completed output to appear.
Environment:
- Platform: macOS 26
- Codex desktop app: installed in
/Applications/Codex.app
- CLI used: app-bundled binary exposed on PATH via symlink to
/Applications/Codex.app/Contents/Resources/codex
- Codex home/session state: default
~/.codex
What variant of Codex are you using?
App and CLI
What feature would you like to see?
I use both the Codex desktop app and the Codex CLI on the same Mac. When I start a new CLI conversation from a folder that already exists as a Codex app project, the desktop app notices the new chat immediately. The chat appears in the project sidebar with the first prompt. After that, the app does not appear to keep refreshing the externally updated thread: it does not show that the CLI turn is running, does not stream or otherwise indicate progress, and does not load the assistant response after the CLI finishes.
The requested feature is for the desktop app to live-refresh local sessions that are created or updated by standalone CLI processes.
Ideally:
Refresh threadorReload project sessionsaction in both the conversation window (replace in the "chat is running in CLI"), and in the sidebar with either an "unread" indicator, or a new indicator specific for this new behavior. The refresh thread action should also be available from the chat context menu in the sidebar.This would make the app and CLI work together as one coherent local workflow. Some work is easier to start from a terminal, while reviewing sessions and switching projects is often easier in the app. Since the app already detects the new CLI-created chat, it is surprising that the visible thread stays stale until the app is restarted.
Additional information
Observed behavior:
codex --cd /path/to/project.What happens today:
Environment:
/Applications/Codex.app/Applications/Codex.app/Contents/Resources/codex~/.codex