skills not detected on Windows with symlink or junctions
Resolved 💬 1 comment Opened Dec 21, 2025 by joshmouch Closed Dec 21, 2025
What version of Codex is running?
0.76.0
What subscription do you have?
Pro
Which model were you using?
N/A
What platform is your computer?
Microsoft Windows NT 10.0.26220.0 x64
What issue are you seeing?
Using a symlink or a junction on windows to "add" a skill to Codex CLI does not work. Codex will not detect the skill. This same skill can be copied as a real folder and be detected.
What steps can reproduce the bug?
- Try either one of the following:
- Symlink
New-Item -ItemType SymbolicLink -Path "~\.codex\skills\.system\{folder-of-skill-under-development}" -Target "{absolute-path-to-folder-of-skill-under-development}"
- Junction
New-Item -ItemType Junction -Path "C:\Users\josh\.codex\skills\.system\evolv" -Path "~\.codex\skills\.system\{folder-of-skill-under-development}" -Target "{absolute-path-to-folder-of-skill-under-development}"
- Enter codex CLI. Type /skills
- List does not show new skill.
What is the expected behavior?
- Enter codex CLI. Type /skills
- List shows new skill
Additional information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗