Codex Desktop pet becomes oversized and clips the running status bubble

Open 💬 1 comment Opened May 18, 2026 by stargif

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

26.513.31313 (CFBundleVersion 2867)

What subscription do you have?

Not provided

What platform is your computer?

Darwin 25.1.0 arm64 arm

What issue are you seeing?

The Codex Desktop pet unexpectedly became much larger than usual. Once enlarged, it takes up most of the pet overlay area and the running/status message bubble above it can no longer show the full text.

Observed from the report context:

  • The pet avatar is rendered very large in the overlay.
  • The activity/status bubble at the top is truncated, so the current running message is only partially visible.
  • The issue affects readability of task progress/status updates while the pet is visible.

What steps can reproduce the bug?

  1. Open Codex Desktop on macOS.
  2. Show or use the desktop pet while a task is running.
  3. Let the pet display a longer running/status message.
  4. Observe that the pet is oversized and the status bubble text is clipped/truncated.

I am not sure what action caused the resize; it appeared unexpectedly rather than through an intentional size setting.

What is the expected behavior?

The desktop pet should keep a stable, reasonable default size, and the running/status bubble should remain readable. Longer status text should wrap, resize, or otherwise remain visible instead of being clipped by the oversized pet overlay.

Additional information

I searched existing issues before filing. The closest related issues I found were about adding resize controls or other pet clipping/rendering problems, but this report is specifically about an unexpected size increase causing the status bubble to become unreadable.

A screenshot was provided in the original report, but I am not attaching it here because it may contain local task text. The visible symptom was an oversized pet with the top status bubble truncated.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗