openai / openai/codex

[Windows] Custom v2 desktop pet cannot be clicked or dragged and may become invisible after switching

Open
#41,519 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug pets windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

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

26.825.4187.0

What subscription do you have?

ChatGPT Plus

What platform is your computer?

No response

What issue are you seeing?

Description

On Windows, a valid custom Codex v2 pet is visible in the bottom-right corner, but it cannot receive mouse input. The pet cannot be clicked or dragged.

The same pet asset works after applying a local workaround to the desktop pet window’s pointer-interactivity behavior, suggesting that the problem is in the Codex desktop app’s Windows hit-testing/input-region handling rather than in the pet asset itself.

Environment

  • OS: Windows
  • Codex desktop app: Microsoft Store version
  • App version observed: 26.825.4187.0
  • Pet format: Codex custom pet v2
  • Feedback correlation / task ID: 01a04c2f-744d-7642-a4be-a4a9b7b02cea

Steps to reproduce

  1. Install and open the official Codex desktop app from the Microsoft Store.
  2. Add or select a valid custom v2 animated pet.
  3. Let the pet appear in the bottom-right corner of the desktop.
  4. Move the mouse over the visible pet.
  5. Try to click and drag it.

Expected behavior

The visible pet should receive pointer input and should be draggable.

Actual behavior

The pet is rendered and animated, but it does not receive mouse input. Clicking or dragging it has no effect.

After switching to another pet, the pet may remain positioned in the bottom-right corner but become invisible and still cannot be clicked or dragged.

Validation performed

  • The custom pet atlas passed validation successfully:
    • Sprite format: v2
    • Dimensions: 1536 × 2288
    • Grid: 8 × 11
    • Format: WebP RGBA
    • Validation result: no errors or warnings
  • The installed pet file hash matched the validated source file.
  • Windows hit-testing over the visible pet returned no interactive hits in the official Store build.
  • After applying a local workaround to the pet overlay’s pointer-interactivity/input-region handling, the same pet became draggable.
  • Manual testing confirmed that dragging worked with the workaround enabled.

Additional context

This appears to be a Windows-specific compatibility issue involving the pet overlay window and APIs such as pointer interactivity, input shape, or ignored mouse events.

The workaround is not a permanent solution because a Microsoft Store update may overwrite it. It would be helpful if the official app could ensure that visible, non-transparent pet pixels remain inside the interactive input region.

Please let me know if additional logs, screenshots, the validated pet atlas, or reproduction files would be useful.

What steps can reproduce the bug?
  1. Install and launch the official Microsoft Store version of Codex on Windows.
  2. Add and select a valid custom v2 animated pet.
  3. Wait for the pet to appear in the bottom-right corner of the desktop.
  4. Try to click and drag the pet. The pet may be visible, but it does not respond to mouse input.
  5. Switch from the custom pet to another pet.
  6. Switch back to the custom pet.
  7. The custom pet is still positioned in the bottom-right area, but it is no longer visible.
  8. Clicking or dragging the area where the pet should be has no effect.
  9. Restarting Codex does not reliably restore the pet’s visibility or interactivity.
What is the expected behavior?

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the Microsoft Store Windows build with a valid custom Codex v2 pet, then inspect the desktop pet overlay's pointer-interactivity and input-region handling. Done means visible pet pixels receive clicks and dragging, and switching pets does not leave the custom pet invisible or non-interactive.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.