Unable to create custom "/" commands.
Resolved 💬 6 comments Opened Dec 13, 2025 by michaelwa Closed Dec 14, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
v0.72.0
What subscription do you have?
plus
Which model were you using?
gpt-5.1-codex-max medium
What platform is your computer?
Linux 6.17.4-76061704-generic x86_64 x86_64
What issue are you seeing?
i do not have access to the features described in the documentation, custom "/" commands.
What steps can reproduce the bug?
Uploaded thread: 019b1984-
What is the expected behavior?
ability to run custom "/" commands from either "prompts" or "tools".
Additional information
_No response_
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
We're not aware of any problems with this feature. Many codex users depend on it. Perhaps this is a configuration issue.
Can you describe the specific steps you've tried?
Here is an overview of my setup.
[image: image.png]
When I type in other "/" commands there is an indicator below.
[image: image.png]
When I type "/prompts" there is no indicator that there is "/" command
starting with these letters.
[image: image.png]
codex version is codex-cli 0.72.0.
Not sure what else I can provide here but let me know.
On Sat, Dec 13, 2025 at 1:20 PM Eric Traut @.***> wrote:
You can try configuring the
codex_homepath, or try reinstalling vianpm install -g @openai/codex@0.72.0. After that, verify that the absolute path to~/.codex/prompts/example.mdis correct.Okay, that helped me identify where I went wrong. The font in the
documentation made the "~" hard to read when creating the prompts
directory. It needs to be in the ~/.codex directory and not in
<project>/.codex directory. Which seems strange to me that mean prompts can
only be global rather than project specific.
Thank you for your help!
On Sun, Dec 14, 2025 at 8:06 AM Proview @.***> wrote:
<img width="415" height="145" alt="Image" src="https://github.com/user-attachments/assets/f8cec95e-1167-4585-a349-cefee6d7284a" />
LMAO. wtf a ~ can be mistakenly read for the fonts hard to distinguish.
the "~" and the "-" ought to have its distinct appearance.