Windows pet overlay loses its hit region after the first drag

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

Build 26.825.5331.0

What subscription do you have?

Pro plan

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

Windows pet overlay loses its hit region after the first drag. The first drag after restart or Wake Pet works; subsequent clicks pass through while animation continues. Reproduces with built-in and custom pets at every scale. Build 26.825.5331.0, Windows 10 build 19045, three 1920×1080 monitors.

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a04c97-8764-7990-ab27-d88d8b0b7570

What is the expected behavior?

The pet should remain interactive after every completed drag.

After releasing the pointer:

1. The next pointer-down event on the visible pet should start another drag.
2. The native hit region should follow the pet window’s final position.
3. Transparent parts of the overlay may remain click-through, but the pet’s designated hit region must continue accepting pointer input.
4. Behavior should be identical for built-in and custom pets, at every supported scale and on every connected display.
5. Restarting the app or recreating the pet overlay should not be required between drags.

Additional information

Feedback ID: no-active-thread-01a04c97-8764-7990-ab27-d88d8b0b7570

1. What steps can reproduce the bug?

Environment:

• OS: Windows 10 Pro for Workstations, build 19045
• Desktop app package: 26.825.5331.0
• Embedded app version: 26.825.41651, build 7345
• Electron: 42.3.0
• Display configuration: three 1920×1080 monitors at 100% scaling
• The problem affects both built-in and local custom pets at every tested pet scale.

Reproduction steps:

1. Fully quit and restart the desktop app.
2. Open Settings → Pets and wake any pet.
3. Press and drag the pet to another position.
4. Release the pointer. The first drag works correctly.
5. Without restarting or recreating the pet overlay, try to drag the same pet again.
6. The pet no longer receives pointer input. Clicking or dragging passes through the overlay to the application underneath.
7. The pet animation continues normally.
8. Restarting the app, or using Tuck Away Pet followed by Wake Pet, restores interaction for exactly one more drag. The problem then repeats.

No user code or prompt is required to reproduce the issue. Equivalent pseudocode:

restartDesktopApp()
wakePet(anyBuiltInOrCustomPet)

drag(pet, positionA, positionB) // succeeds
drag(pet, positionB, positionC) // fails: pointer input passes through

assert(pet.animationIsStillRunning)

The same behavior was observed before and after the application updated from package 26.825.4187.0 to 26.825.5331.0.

Session ID: Not available.
Token limit usage: Not applicable.
Context window usage: Not applicable.

This is a native desktop overlay interaction bug and does not depend on a conversation, prompt, model, token limit, or context-window usage.

Start by reproducing the drag sequence on Windows with a built-in or custom pet, then trace the desktop app's pet overlay drag and native hit-region lifecycle. Verify that after each pointer release the visible pet accepts another pointer-down, its hit region follows its final position, and transparent areas remain click-through without requiring restart or Tuck Away/Wake Pet.