Recommended skills and WSL workspace git detection fail with mixed WSL paths and partial vendor_imports recovery
Resolved 💬 3 comments Opened Mar 13, 2026 by lczanna Closed Mar 13, 2026
What version of the Codex App are you using (From “About Codex” dialog)?
OpenAI.Codex 26.309.3504.0
What subscription do you have?
API
What platform is your computer?
Windows: Microsoft Windows NT 10.0.26100.0 x64 WSL: Linux x86_64 x86_64 GNU/Linux
What issue are you seeing?
Summary
In a WSL-backed workspace, Codex desktop repeatedly fails to load recommended skills and also fails workspace git/origin detection.
Expected
- Recommended skills should load or recover cleanly.
- Git root/origin detection should work for WSL workspaces.
- Partial
vendor_imports/skillsstate should be repaired automatically.
Actual
The app shows repeated recommended-skills failures and git/origin resolution failures.
What steps can reproduce the bug?
Repro
- Launch Codex desktop on Windows.
- Open or reopen a WSL-backed workspace.
- Trigger skill loading or recommended skills refresh.
- Observe repeated recommended-skills warnings and git/origin failures.
Evidence
Observed failures include:
git clone failed: destination path 'C:\Users\<user>\.codex\vendor_imports\skills' already exists and is not an empty directorygit fetch failed ... chdir(/mnt/c/Users/<user>/.codex/vendor_imports/skills) failed 2fatal: not a git repositoryUnable to create '/mnt/c/Users/<user>/.codex/vendor_imports/skills/.git/shallow.lock': File existsFailed to resolve git root: Unknown errorENOENT: path does not exist: /home/<user>/<workspace>
Additional context
The app state appears to contain both:
\\wsl$\Ubuntu\home\<user>\<workspace>\\wsl.localhost\Ubuntu\home\<user>\<workspace>
This may indicate mixed path handling for the same workspace.
Environment
- Codex desktop version:
26.309.3504.0 - Windows:
Windows 10, build26100 - WSL:
Ubuntu, version2 - Git installed on Windows
What is the expected behavior?
_No response_
Additional information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗