codex - 💡(How to fix) Fix Allow CLI to use skills as first token in prompt - Remove "Unrecognized 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#17796Fetched 2026-04-15 06:28:06
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×4closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.120.0

What subscription do you have?

Pro

Which model were you using?

No response

What platform is your computer?

No response

What terminal emulator and version are you using (if applicable)?

No response

What issue are you seeing?

If you start a message to codex with a valid command i.e. /babysit-pr it fails with "Unrecognized command"

So you have to add a token in front like, "use" when really that should not be necessary.

Sometimes, I specifically want to start a sentence with a skill like,/test this new feature, which is like a rather large verb behind that but the AI will absolutely get it once it processes the skill.

However, this is not allowed...for seemingly historical reasons when commands and skills had to be treated 100% differently.

What steps can reproduce the bug?

Create a valid skill, invoke it in the middle of a sentence. Do it again at the start. it fails.

What is the expected behavior?

It simply processes the skill as it otherwise would.

Additional information

No response

extent analysis

TL;DR

The issue can be worked around by adding a token like "use" before the command, but a more robust solution would involve updating the Codex CLI to handle commands and skills more flexibly.

Guidance

  • The issue seems to stem from the historical distinction between commands and skills, which is no longer necessary, suggesting a potential update to the command parsing logic.
  • To verify the issue, create a valid skill and try invoking it at the start and middle of a sentence, observing the different behaviors.
  • Consider reaching out to the Codex CLI development team to report this issue and request an update that allows for more flexible command and skill handling.
  • In the meantime, adding a token like "use" before the command can serve as a temporary workaround.

Example

No code snippet is provided as the issue does not involve specific code but rather the behavior of the Codex CLI.

Notes

The solution involves either updating the Codex CLI or using a workaround, but without more information about the development roadmap or internal workings of the CLI, it's difficult to provide a more definitive fix.

Recommendation

Apply workaround: Adding a token like "use" before the command is a straightforward way to circumvent the current limitation, although it's not an ideal long-term solution.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING