Regression: app-server conversations are classified under ChatGPT Work instead of Codex

What issue are you seeing?

After the ChatGPT/Codex desktop integration upgrade, conversations created through a custom Codex app-server bridge are classified under ChatGPT Work instead of Codex.

This is a regression. Before the upgrade, the same communication workflow created conversations under the Codex category. With the current runtime, the conversation is created successfully and can be read and resumed, but it appears under the wrong product/category in the desktop UI.

We also tried passing threadSource: "user" to thread/start. This value is persisted as thread_source=user, but it does not change the desktop classification.

What steps can reproduce the bug?

1. Use the following environment:

• ChatGPT Desktop app: 26.715.61943 (build 5628)
• Codex CLI bundled with ChatGPT Desktop: 0.145.0-alpha.27
• macOS 26.5.2 arm64

1. Start a custom JSON-RPC client using the Codex app-server over stdio:

``bash
codex app-server --stdio
``

1. Complete the initialize handshake.
2. Create a new thread with threadSource: "user":

``json
{
"cwd": "<redacted>",
"approvalPolicy": "on-request",
"sandbox": "workspace-write",
"threadSource": "user"
}
``

1. Start a turn with turn/start.
2. Open the resulting conversation in the Codex desktop app.

What is the expected behavior?

The conversation should remain under the Codex category, as it did before the ChatGPT/Codex integration upgrade.

If the classification behavior intentionally changed, there should be a documented app-server parameter or client integration requirement for selecting the Codex category.

What is the actual behavior?

The conversation appears under ChatGPT Work instead of Codex.

For example, the following locally persisted thread was created through the custom app-server bridge:

thread id: 019f83a5-9058-7d21-a0a6-6c0f486db3f0
source: vscode
thread_source: user
cli_version: 0.145.0-alpha.27

Passing threadSource: "user" changes the stored thread_source value but does not affect the visible category.

Older conversations created before the upgrade were stored with source=exec and appeared under Codex.

Additional information

This appears related to:

• https://github.com/openai/codex/issues/13951
• https://github.com/openai/codex/issues/16614

Those reports also describe Codex App or custom app-server conversations being persisted as source: "vscode", but they do not specifically address the visible regression from the Codex category to ChatGPT Work.

Could you clarify whether the ChatGPT/Codex integration changed the product attribution for app-server-created conversations, and how a custom app-server client can preserve the Codex category?