Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex Desktop: installed hatch-pet skill is not discoverable from slash command autocomplete [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#20778•Fetched 2026-05-03 04:45:39
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Kekeu-uKekeu-u
Participants
github-actions[bot]github-actions[bot]Kekeu-uKekeu-u
Timeline (top)
labeled ×4commented ×1

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.

Root Cause

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.

RAW_BUFFERClick to expand / collapse

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

  1. Install the curated hatch-pet skill into ~/.codex/skills/hatch-pet.
  2. Restart Codex Desktop.
  3. Open the composer and type /hatch.
  4. 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.

extent analysis

TL;DR

The issue may be resolved by using the full skill name, such as /hatch-pet, in the composer instead of the partial name /hatch, or by consulting the documentation for the correct invocation method.

Guidance

  • Verify that the skill is correctly installed in ~/.codex/skills/hatch-pet and that the Codex Desktop has been restarted after installation.
  • Check the documentation for the correct way to invoke installed skills, as it may not be through slash commands.
  • Test using the full skill name, such as /hatch-pet, to see if it is discoverable in the composer.
  • Consider consulting the plugin-provided command discovery documentation for local plugins to see if there are specific requirements for skill invocation.

Notes

The issue may be related to a lack of clear documentation on how to invoke installed skills, rather than a technical issue with the skill installation itself.

Recommendation

Apply workaround: Use the full skill name, such as /hatch-pet, or consult the documentation for the correct invocation method, as the issue may be due to unclear documentation rather than a technical problem.

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…

FAQ

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.
#embedding generation#cache error#pipeline error#runtime error#dependency conflict

Still need to ship something?

×6

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

Back to top recommendations

TRENDING