›_ Codex Issues
Codex Issues / #34309

[Windows] Pets cannot be dragged in Codex 26.715.4045, including default pet

Open 💬 6 comments Opened Jul 20, 2026 by Plop90
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Codex version: 26.715.4045
Platform: Windows desktop
Display setup: One display, 1920×1080
Previous working version: 26.715.2305

Actual:
No pet can be dragged. This affects the built-in default pet and every
custom pet. Restarting Codex, resetting placement, switching pets, and
forcing non-native rendering did not help.

Expected:
The pet should become interactive when hovered and move when dragged.

Diagnostics:
The pet overlay remains click-through (WS_EX_TRANSPARENT). It begins
non-interactive and does not transition out of mouse passthrough, so
pointer-down and drag-start events never reach the renderer.

This appears to be a shared Windows overlay regression rather than a pet
asset or monitor-position problem. macOS works because it uses a separate
native cursor/drag bridge.

Related: #21359, but this reproduction does not require a secondary display.

Uploaded Codex session ID: [PASTE SESSION ID]

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #34227

Powered by Codex Action

khoopl · 1 month ago

Consolidating this report into #34227.

17jiangyiqi-hash · 1 month ago

Confirming the same regression on a newer Windows package.

Environment

  • Codex Desktop package: OpenAI.Codex 26.715.10079.0
  • Platform: Windows x64
  • Previous installed package: 26.715.7063.0 (dragging worked before the update)

Reproduction and scope

  1. Wake/show the desktop pet.
  2. Move the pointer over the visible mascot: the pet reacts and plays its jump animation.
  3. Hold the primary mouse button on the mascot and move the pointer.
  4. The mascot does not move and no drag begins.

This reproduces with both:

  • a validated custom v2 pet; and
  • Codex's bundled/default pets.

Fully restarting Codex, restarting Windows, and switching between custom and bundled pets do not restore dragging.

Important distinction

Pointer hit testing is not completely lost: hover/click interaction still reaches the pet because hovering triggers the jump animation. The failure appears specific to the drag-start/native window-drag transition, rather than the pet asset or the whole overlay remaining click-through.

Local technical observation

The packaged Windows renderer dispatches the avatar drag-start/move/end path and calls compositionHost.performWindowDrag(). When that native call reports success, the renderer-side fallback movement is skipped. Given that hit interaction still works but neither bundled nor custom pets move, this may be a regression in the native composition window-drag path or its success reporting.

No personal logs or pet assets are attached.

saru-soft · 7 hours ago

I’m experiencing the same regression in the latest Codex Desktop update on Windows: the floating Pet cannot be moved/dragged at all.

This is a major usability issue because the Pet can remain directly over the main work area and block the screen. The only practical workaround is to disable/close the Pet entirely, which removes the feature rather than solving the positioning problem.

Expected behavior:

  • The Pet should respond to mouse interaction and be draggable to another position.
  • After dragging, it should remain movable and not block the user’s workspace.

Please prioritize a fix or provide a way to reset/reposition the Pet through settings or a keyboard command.

stephenjeffreywhite · 5 hours ago

Having same problem as the others, started with latest codex update as of today. Submitted feedback in app, reference number: 019fd9be-8e3c-7100-8c0c-0e1612e93b8f

Here's hoping this gets fixed soon, the only workaround is to hide my pet, which as @saru-soft mentioned, basically nullifies the feature.

colthreepv · 24 minutes ago

+1 — still reproducible on Windows after today’s update, Codex Desktop 26.825.4187.0.

The pet is completely click-through: I can neither drag it nor click its notification/activity items. This affects the normal built-in pet, so it does not appear to be a custom-pet issue.