Codex Desktop /pet is sent as a normal chat message instead of triggering pet command

What version of the Codex App are you using?

Codex Desktop 26.429.30905, build 2345.

What platform is your computer?

macOS 26.3.1 build 25D771280a, Apple Silicon / arm64.

What issue are you seeing?

Pets appears in Codex Settings, but typing /pet in the composer is not handled as a slash command. Instead, /pet is sent into the conversation as a normal chat message.

This makes the installation feel inconsistent: the Pets feature is visible in Settings, but the documented /pet command does not appear to be registered or exposed in the composer.

What steps can reproduce the bug?

1. Open Codex Desktop on macOS.
2. Confirm that Pets appears in Settings.
3. Open any Codex conversation.
4. Type /pet into the composer.
5. Submit it.

What is the expected behavior?

/pet should be intercepted by the composer slash-command system and should wake or tuck away the desktop pet.

What is the actual behavior?

/pet is sent as a regular user message to the assistant.

Additional information

Local CLI version: codex-cli 0.128.0-alpha.1.

I searched related issues. #20706 looks similar but not identical: that report says /pet appears in autocomplete but does not show the pet. In this case, /pet is not being handled by the composer at all and is delivered as a normal chat message.

While inspecting the packaged app, I saw references to composer.petOverlaySlashCommand with id pet, triggering openAvatarOverlay, and guarded by what appears to be feature gate 2679188970. This may be a rollout/gate mismatch between Settings and the composer slash-command registration.