$ skill selector shows duplicate skills with same name across scopes without indicating which one wins precedence

Open 💬 1 comment Opened Jan 26, 2026 by alperenYagci

What version of Codex is running?

v0.91.0

What subscription do you have?

plus

Which model were you using?

5.2

What platform is your computer?

Linux 6.18.6-200.fc43.x86_64 x86_64 unknown

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

gnome terminal

What issue are you seeing?

In the Codex CLI, the $ skill mention/selector UI shows duplicate entries when a skill with the same name exists in multiple scopes (e.g., REPO and USER). This is confusing because skill precedence says the higher-precedence location should override the lower one, but the selector provides no indication which entry wins or which one will run when selected.

Note: /skills looks fine in my case — the issue is specifically the $ selector.

What steps can reproduce the bug?

  1. Create a skill in the repo scope:
  • <repo>/.codex/skills/my-skill/SKILL.md
  • with:

``yaml
---
name: my-skill
description: test
---
``

  1. Create another skill in the user scope with the same name:
  • ~/.codex/skills/my-skill/SKILL.md
  • with the same YAML name: my-skill
  1. Start Codex CLI from inside the repo.
  2. Type $ to open the skill mention/selector UI.
  3. Observe that two my-skill entries are shown.

What is the expected behavior?

When multiple skills share the same name, the $ selector should either:

  • Show only the resolved/active skill (the one that wins precedence), or
  • Show both entries but clearly label them with:
  • which one is Active (wins precedence)
  • which one is Overridden
  • and include scope + full path so the user can intentionally choose.

Current behavior (duplicates with no disambiguation) makes explicit invocation ambiguous.

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗