Custom prompts in ~/.codex/prompts no longer appear after updating to codex-cli 0.117.0

Resolved 💬 7 comments Opened Mar 27, 2026 by zhouzhendiao Closed Mar 27, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.117.0

What subscription do you have?

plus

Which model were you using?

codex-cli 0.117.0

What platform is your computer?

Linux

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

VSCode

What issue are you seeing?

Custom prompts in ~/.codex/prompts no longer appear in the slash-command menu after updating Codex.

This worked before the update. After updating to codex-cli 0.117.0, the prompt is not discoverable anymore, even after restarting Codex.

What steps can reproduce the bug?

  1. Create a custom prompt file at ~/.codex/prompts/commit.md
  2. Use content like:

```md
---
description: Auto add and commit changes based on session history and current git status.
---
# Commit

Auto add and commit changes.

Based on the session history, decide whether to:

  • add and commit only the files related to the session, or
  • add all changed files and commit them.
  1. Fully restart Codex
  2. Open the slash command menu
  3. Try to invoke the prompt with /prompts:commit

What is the expected behavior?

The custom prompt should appear in the slash command menu and be invokable as /prompts:commit.

Additional information

The custom prompt should appear in the slash command menu and be invokable as /prompts:commit.

### What do you see instead?

The prompt does not appear at all.

### Additional information

  • The file definitely exists at ~/.codex/prompts/commit.md
  • I also tested plain markdown and markdown with YAML frontmatter
  • I restarted Codex after editing the file
  • My ~/.codex/config.toml does not appear to disable custom prompts
  • This worked before I updated Codex, so this looks like a regression

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 3 months ago

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

  • #15939
  • #14459

Powered by Codex Action

etraut-openai contributor · 3 months ago

We previously announced that custom prompts were deprecated. They have been removed completely starting in 0.117.0. You should convert your custom prompts to skills. Codex can do the conversion for you.

zhouzhendiao · 3 months ago

Thanks!

aceHubert · 3 months ago

codex cli read .agent/skills as well,
./codex/skills makes skills duplicated

muqsitnawaz · 2 months ago

Pretty interesting design choice given that LLMs are probablistic token machines so even asking a GPT model to invoke a Skill doesn't guarantee that the Skill will actually be loaded and executed

Slash commands/prompts on the other hand had a well-defined syntax and were pretty lightweight as opposed to a skill or a plugin. Worse, for the '$' based syntax that surfaces suggestions to the user, it's now suggesting from a huge superset of officially published Codex Apps and GPT Plugins

ashe0047 · 2 months ago

The custom command is so useful, why is it being deprecated, bad design choice

etraut-openai contributor · 2 months ago

@ashe0047, you can write custom commands as skills. It doesn't make sense to provide two overlapping features and mechanisms that do the same thing. The industry has rallied behind skills as a standard.