Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex Desktop /pet is sent as a normal chat message instead of triggering pet command [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20836•Fetched 2026-05-04 05:09:41
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
1
Author
zqchriszqchris
Participants
github-actions[bot]github-actions[bot]zqchriszqchris
Timeline (top)
labeled ×3commented ×1
RAW_BUFFERClick to expand / collapse

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.

extent analysis

TL;DR

The issue may be resolved by ensuring that the feature gate 2679188970 is properly enabled for the composer slash-command registration to handle the /pet command.

Guidance

  • Verify that the composer.petOverlaySlashCommand is correctly configured and enabled in the Codex Desktop application.
  • Check the feature gate 2679188970 to ensure it is not causing a rollout mismatch between Settings and the composer slash-command registration.
  • Investigate the codex-cli version 0.128.0-alpha.1 to see if it has any known issues related to slash command handling.
  • Compare the behavior with the related issue #20706 to identify any potential similarities or differences in the root cause.

Example

No code snippet is provided as the issue does not contain sufficient information to create a relevant example.

Notes

The issue may be specific to the macOS platform or the Apple Silicon architecture, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Investigate and adjust the feature gate 2679188970 to ensure proper registration of the /pet slash command in the composer, as this appears to be the most likely cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#installation#memory optimization#batch processing#GPU compatibility#latency issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex Desktop /pet is sent as a normal chat message instead of triggering pet command [1 comments, 2 participants]