On Windows 11 + Ubuntu WSL2, if the Agent chat workspace root is a WSL path (e.g. \wsl.localhost\Ubuntu\home...\project), typing / shows none of my personal commands or skills.
Those files exist on the Windows host under %USERPROFILE%.cursor\commands and .cursor\skills, and they appear when the workspace root is a normal Windows folder.
Update: Commands and skills now appear in the input box after a later Reload Window. Earlier reloads and a new session did not resolve it. I had also added project-level commands and skills, so I cannot yet confirm whether Windows personal entries are being loaded or which change mattered.
The logs showed repeated WSL management socket timeouts and a remote extension host that did not become ready within 60 seconds. This may have contributed, but the root cause is not confirmed. Some socket timeouts continued after the reload.
Hey, good that it started working. From your logs WSL socket timeouts and the remote extension host not starting within 60s, it looks like the empty / was related to the WSL connection. In a WSL project, the list depends on whether the WSL side is ready. Until the connection comes up properly, the menu can stay empty, and that Reload Window likely helped because the connection succeeded cleanly after that.
When the connection is healthy, the two types of personal entries behave differently:
Personal commands are read from Windows at %USERPROFILE%\.cursor\commands, so they should also show up in WSL projects.
Personal skills are looked up in the home directory of the environment where the agent is running. For a WSL project, that means your Ubuntu home at ~/.cursor/skills, not your Windows profile.
To keep one set of skills on both sides, you can create a symlink from inside WSL and then do Reload Window:
If there is already something in ~/.cursor/skills in WSL, move it somewhere else first. Also note that if you create user skills through Customize in a WSL window, they get saved on the Windows side. So for WSL, it’s better to create them directly in the Linux home, or use the symlink above. The same approach is described in this thread: Unify personal Agent Skills across Windows host and WSL (Remote)
Could you check two things after that?
Remove the project-level copies of commands and see whether the Windows personal commands appear in the WSL project when WSL is connected.
If the menu goes empty again, send the WSL logs from the Output panel from that moment.