codex - 💡(How to fix) Fix Codex Desktop on Windows can route Codex-bound text into an unrelated external browser input

What version of the Codex App are you using?

• Windows app package: OpenAI.Codex_26.513.4821.0_x64__2p2nqsd0c76g0
• App executable product version observed from process list: 26.513.40821
• Bundled Codex CLI/process version observed from process list: 0.131.0-alpha.9

What platform is your computer?

• Windows 11 Home Chinese edition
• Microsoft Windows NT 10.0.26200.0 x64
• OS build: 26200

What issue are you seeing?

Codex Desktop appears to sometimes route text that should be written/sent inside the Codex conversation into an unrelated normal browser window that is open on the desktop.

This was not the Codex in-app browser. It was a separate regular browser window with a web chat/input area. Text intended for Codex was inserted/sent into that external browser conversation instead.

Observed examples included:

• an email-style reply that should have stayed in the Codex conversation appearing in the external browser chat
• a Windows local artifact path for a .hap file appearing in the external browser chat; the real path included a user profile path and Chinese workspace characters, but I am redacting it here as C:\Users\<user>\Desktop\<workspace>\...\entry-default-release-api21-signed.hap
• the same local path was posted more than once

I am not attaching the screenshot publicly because it contains private conversation text and local filesystem paths, but the screenshot clearly shows the browser conversation receiving the Codex-bound text.

Why this matters

This is a privacy/security issue, not just a UI annoyance. If Codex-bound text is sent to a non-target external browser window, it can leak:

• local filesystem paths
• repository/workspace names
• task details
• draft emails or messages
• other private content that the user expected to remain inside Codex

What steps can reproduce the bug?

I do not yet have a minimal deterministic repro, but the observed situation was:

1. Use Codex Desktop on Windows.
2. Have a separate regular browser window open with a web chat/input field. This is not the Codex in-app browser.
3. Continue working in Codex Desktop and have Codex generate/send text that should remain in the Codex conversation.
4. Observe that some Codex-bound text is inserted/sent into the unrelated browser chat instead.

Expected behavior

Codex Desktop should never send Codex conversation text, generated output, file paths, or tool-result text to an unrelated OS-level browser window or web input field.

Before injecting, pasting, or sending any text, Codex should verify that the target control is the Codex chat/composer or the explicitly intended target. If focus has moved to another application/window, Codex should fail locally or ask the user to refocus rather than sending text to that external app.

Actual behavior

Text that should have appeared only in the Codex conversation was posted into an unrelated normal browser chat.

Related but not duplicate

I found related issues around wrong-window capture or browser automation focus, such as #21668 and #16188, but this report is specifically about Codex-bound text being routed into an external normal browser input, which can directly leak private data.