[macOS][Pets] Pet becomes invisible after lock/unlock on a three-display setup (26.911.61220)

What version of the Codex App are you using?

26.911.61220 (build 9647), as reported by the installed desktop app's Info.plist. The installed bundle is named ChatGPT.app (com.openai.codex).

What subscription do you have?

Not collected for this report.

What platform is your computer?

macOS 26.6.2 (25G83), with three displays: a built-in display and two external displays, one in portrait orientation. External displays extend above the built-in display in the desktop arrangement.

What issue are you seeing?

The desktop pet repeatedly becomes invisible after locking and unlocking macOS. The owner reports this happens on each lock/unlock cycle. During inspection after an affected cycle, the pet was absent from screenshots of all three displays, but its native overlay window still existed. Moving that window restored the rendered pet.

This may be another reproduction of #43404, specifically triggered by lock/unlock and still occurring on build 9647. Please merge/close as a duplicate if the underlying issue is the same.

What steps can reproduce the bug?

1. Use the desktop app with the three-display arrangement described above.
2. Enable the desktop pet and place it where it is visible.
3. Lock macOS, then unlock and return to the desktop.
4. Observe that the pet is no longer visible on any display.
5. Manually reposition the existing pet overlay window; the pet renders again. The owner reports that a subsequent lock/unlock brings the problem back.

The exact lock duration and whether each occurrence includes system sleep were not recorded.

What is the expected behavior?

The pet remains visible on its intended display/Space after unlocking, without manual window repositioning.

Additional information

Observed native window geometry during one affected state, in macOS accessibility coordinates:

pet overlay: x=1180, y=-1437, width=772, height=5029
main window: x=1799, y=-863, width=1441, height=1265

Moving only the overlay to x=2130, y=-3380, while retaining its dimensions, made the pet visible on the portrait display. The large transparent window size alone is not proof of a bug; it may be intentional drawing padding. The useful observation is that repositioning the existing window restored visibility without changing pet assets or restarting the application.

Inspection of the shipped bundle found that the avatar overlay listens for suspend/resume and display changes. Its local power-monitor registration did not include lock-screen/unlock-screen. This is an investigation lead only: other application-level handlers may exist, and missing lock/unlock listeners have NOT been established as the root cause. Native window geometry and display/Space association are also plausible factors, especially given #43404.

A local polling workaround was installed after the observations above, but it has not passed a controlled lock/unlock regression test and should not be treated as a confirmed fix. No application bundle or pet assets were modified.

Screenshots are omitted because the desktops contain private work. No session content or credentials are included.

Start by reproducing the lock/unlock cycle with the three-display arrangement and inspect the avatar overlay's suspend/resume, display-change, and power-monitor handlers. Compare the overlay's window geometry and display/Space association before and after unlocking, while checking whether issue #43404 covers the same path. Done means the pet remains visible after repeated lock/unlock cycles without manual repositioning.