-
Notifications
You must be signed in to change notification settings - Fork 10.2k
skills not detected on Windows with symlink or junctions #8400
Copy link
Copy link
Closed as duplicate of#8369
Labels
CLIIssues related to the Codex CLIIssues related to the Codex CLIbugSomething isn't workingSomething isn't workingwindows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems
Description
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
CLIIssues related to the Codex CLIIssues related to the Codex CLIbugSomething isn't workingSomething isn't workingwindows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems