Codex Desktop: installed hatch-pet skill is not discoverable from slash command autocomplete

Open 💬 2 comments Opened May 2, 2026 by Kekeu-u

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

In Codex Desktop on Windows, installed skills such as hatch-pet are not discoverable from the slash-command autocomplete. Typing /hatch in the composer shows "No command" even when the curated skill exists under ~/.codex/skills/hatch-pet.

Environment

Product: Codex Desktop
Windows package: OpenAI.Codex_26.429.3425.0_x64__2p2nqsd0c76g0
Codex CLI: 0.125.0
OS: Windows

Reproduction

Install the curated hatch-pet skill into ~/.codex/skills/hatch-pet.
Restart Codex Desktop.
Open the composer and type /hatch.
The slash-command autocomplete reports no matching command.

Expected behavior

Codex should either:

expose installed skills through deterministic slash-command aliases, for example /hatch or /hatch-pet;
document clearly that skills are not slash commands and should be invoked through $hatch-pet or natural language; or
support plugin-provided command discovery for local plugins in a documented way.

Actual behavior

/hatch is not discoverable in the composer slash menu.

Notes

The curated skill exists upstream in openai/skills at skills/.curated/hatch-pet. I also tested a local plugin with .codex-plugin/plugin.json and markdown command files, installed into ~/.codex/plugins/cache/supar-local/hatch/0.1.0, but the supported command discovery contract for Desktop is unclear.

This may be a product/docs issue rather than a missing skill issue.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 3 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#19427

Powered by Codex Action

smalljimmy · 1 month ago

Adding a macOS and team-scale productivity perspective: this is broader than one installed skill. Teams with many repository, local, and plugin skills currently have to remember and type the exact $skill-name, while the desktop composer autocompletes built-in slash commands and lacks parity with the CLI /skills picker.

This creates recurring discovery and context-switching friction, makes reusable workflows harder to adopt, and is a significant migration and daily-productivity gap for engineering teams coming from Cursor-style custom commands.

Requested UX:

Typing $ opens fuzzy autocomplete across all available skills.
Add the /skills picker to Desktop and IDE surfaces.
Optionally support deterministic aliases such as /review-pr.
Show display name, description, and source, with full keyboard navigation.

Please prioritize this as soon as possible. A Codex feedback payload with additional diagnostics was uploaded under thread ID 019f52dd-0e11-7093-aba8-9115773f708b.