What happened?
Starting pi from a non-C: drive (e.g. E:) produces "[Skill conflicts]" warning with a malformed path like
[Skill conflicts]
E:\C:\Users\xxx\AppData\Roaming\npm\node_modules@\pi-unipi\notify\skills
skill path does not exist
Steps to reproduce
Observed on a setup where pi packages are managed via ~/.pi/agent/npm/package.json and the working directory is on a different drive than home:
- Ensure ~/.pi/agent/settings.json has packages like @pi-unipi/notify installed (via agent npm project, not system global)
- cd E:\project\relwatch (or any directory on a non-C: drive)
- pi
Expected behavior
No warning. Skills load correctly regardless of which drive pi's cwd is on.
Version
0.75.3
I have a fix branch. Can submit a PR if approved.
What happened?
Starting pi from a non-C: drive (e.g. E:) produces "[Skill conflicts]" warning with a malformed path like
Steps to reproduce
Observed on a setup where pi packages are managed via ~/.pi/agent/npm/package.json and the working directory is on a different drive than home:
Expected behavior
No warning. Skills load correctly regardless of which drive pi's cwd is on.
Version
0.75.3
I have a fix branch. Can submit a PR if approved.