[Desktop] “More Details” on selected text in a local Codex task silently creates a cloud Chat conversation

Reproduce the flow in the Codex desktop app by opening a local project task, selecting text, and choosing More Details; compare the observed cloud Chat creation with the expected destination disclosure and confirmation described here. Use the related issues #31966, #32033, #33079, and #33475 for context. Done means cloud Chat is not created silently and the destination is clearly disclosed before an explicit user action.

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

26.715.12143

What subscription do you have?

plus

What platform is your computer?

No response

What issue are you seeing?

In a local Codex project task, selecting text and choosing More Details immediately creates or opens a new cloud Chat conversation.

This is easy to trigger accidentally because the menu action does not clearly say that it will leave the local Codex task context and create a persistent cloud-synced Chat conversation. There is no confirmation step, no visible destination label, and no warning that the selected text/context may be carried into a different conversation surface.

This has several unwanted effects:

It pollutes cloud Chat history with accidental conversations.

It makes the boundary between a local Codex task and cloud Chat unclear.

It is difficult to distinguish an intentional Chat handoff from an accidental text-selection action.

Users who deliberately keep work in local Codex tasks can create cloud conversations unintentionally.

What steps can reproduce the bug?

Open a local project task in the Codex desktop app.

Select any text in the conversation.

Click More Details in the text-selection menu.

Observe that a new cloud Chat conversation is created or opened without an explicit confirmation that this is the destination.

What is the expected behavior?

“More Details” should not silently create a cloud Chat conversation.

At minimum, the app should clearly show the destination before any cloud conversation is created, for example:

Ask in this local Codex task

Create a cloud Chat conversation

Cancel

Creating cloud Chat should require an explicit user action and clearly disclose that it creates a cloud-synced conversation. Ideally, users should also be able to disable this text-selection shortcut or make the local-task behavior the default.

Additional information

This appears related to the broader ambiguity between local Codex tasks and cloud Chat/Work surfaces, but is distinct from existing reports about “More Details → Add to Task” freezing:

https://github.com/openai/codex/issues/31966

https://github.com/openai/codex/issues/32033

https://github.com/openai/codex/issues/33079

https://github.com/openai/codex/issues/33475