[Windows][26.901.5003.0] Built-in and custom pets pass clicks through to the desktop after app restart

What version of the Codex App are you using?

OpenAI.Codex Windows package 26.901.5003.0 (verified from installed package metadata).

What subscription do you have?

Not provided in this report.

What platform is your computer?

Windows 11 Home Chinese, build 26200, x64.

What issue are you seeing?

The floating pet is visible but cannot be clicked or dragged. This affects both a custom pet and the built-in blue pet.

• Attempting to drag the visible body does not move the pet. The user reports that a blue selection rectangle appears behind it and grows with mouse movement.
• Right-clicking the visible body opens the Windows desktop context menu, rather than being handled by the pet.
• A user-supplied screenshot shows the desktop context menu overlapping the built-in blue pet. This supports the reported symptom; the static screenshot does not record the precise click coordinates or native pointer events.

This makes the pet impossible to reposition through normal mouse interaction.

What steps can reproduce the bug?

1. Open Codex on Windows and show a built-in pet on the desktop.
2. Place the mouse over the visible/opaque part of its body.
3. Hold the left mouse button and move the mouse to attempt a drag.
4. Release, then right-click the visible body.
5. Observe that the pet does not move and the desktop receives the interaction.

What is the expected behavior?

The visible pet body should receive mouse input and follow a drag. Interacting with the body should not activate the desktop underneath.

Additional information

Already tried, without restoring interaction:

• Switching between the custom pet and a built-in pet.
• Hiding and waking the pet with /pet.
• Fully exiting and reopening the Codex application.

No Windows reboot, application reinstall, display-scaling change, GPU launch-flag change, or community window-style reset is claimed as a test on this machine. No application-package patch was applied.

The exact cause remains unconfirmed. This report does not establish a particular DPI conversion, input-shape implementation, or window-style flag as the root cause. Earlier visual-artifact observations are excluded because a shared cause has not been established.

Related reports: #42661 and #42061. This adds a reproduction on 26.901.5003.0. Please close as a duplicate if an existing issue already tracks this reproduction.

Only the summarized reproduction is shared here; no private logs, conversation export, screenshots, credentials, or local project paths are attached.

Reproduce the interaction failure on Windows 11 with package version 26.901.5003.0, then inspect the pet window's mouse-input handling and compare related reports #42661 and #42061. Done means both built-in and custom pet bodies receive clicks and drag input after restart without passing events to the desktop.