[Windows] Pet activity badge becomes unclickable after being moved to bottom-right
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- desktop, operating-systems
Research direction
Reproduce the issue with the Windows Codex Desktop pet overlay and the persisted avatar-mascot-notification-badge-corner value set to bottom-end. Start by tracing synchronization between the native badge rectangle and the transparent overlay's renderer hit testing and mouse passthrough state. Done means the bottom-end badge remains clickable and draggable, and its behavior persists correctly after restart.
Written by the indexing model from the issue text.
Description
What version of the Codex App are you using?
Codex Desktop on Windows, Microsoft Store/AppX package version:
26.715.4045.0
What platform is your computer?
- Windows x64
Microsoft Windows NT 10.0.26200.0
What issue are you seeing?
The pet/avatar activity badge (the small circular control used to show or hide the activity tray) becomes effectively unclickable after it is moved from its default top-right position to the bottom-right of the pet.
The badge remains visible near the pet's right foot, but clicking it no longer shows/hides the activity tray, and dragging it back to another corner does not work. The position persists across a full Codex restart.
The persisted value changes to:
avatar-mascot-notification-badge-corner = bottom-end
Changing only that value back to top-end while Codex is fully closed restores normal behavior after relaunch.
This was observed with a custom v2 pet. The circular badge itself is Codex-owned overlay UI rather than part of the pet image.
What steps can reproduce the bug?
- Open the Codex Desktop pet overlay and wait for the circular activity/status badge to appear at the default top-right position.
- Drag or press the badge with enough pointer movement for it to relocate toward the lower-right quadrant of the pet.
- Release it so the saved corner becomes
bottom-end. - Try to click the badge to show/hide the activity tray.
- Try to drag the badge back to the top-right.
- Fully restart Codex and try again.
What is the expected behavior?
All supported badge corners should have the same click and drag behavior. A badge placed at bottom-end should remain clickable and draggable.
What is the actual behavior?
At bottom-end, the badge remains visible but behaves as if mouse input is passing through it. It cannot reliably be clicked or dragged back, and the unusable position persists after restart.
Workaround
- Fully quit Codex.
- In the Codex global state, change only
avatar-mascot-notification-badge-cornerfrombottom-endtotop-end. - Relaunch Codex.
Additional technical observations
bottom-endis accepted and persisted as a valid corner; it is not rejected as unsupported.- The badge uses a very small pointer-movement threshold (approximately 4 px) before a press is treated as a drag. This can explain how the badge is accidentally moved, but not why it becomes unusable afterward.
- The avatar overlay is a transparent/click-through window that switches pointer interactivity based on renderer hit testing.
- The native badge surface appears to be visual-only, so interaction depends on the underlying overlay/DOM hit target.
- The most likely affected area is synchronization between the native badge visual rectangle and the root overlay's hit testing/mouse passthrough state at
bottom-end. This is a suspected cause, not a confirmed root cause.
I searched existing open issues before filing. The closest reports I found were #21864 (pet resizing) and #21088 (invisible pet sprite on macOS), but neither describes this bottom-right badge input failure.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·