You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6dd68c6
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): change skills under the filesystem write scope, and check tracking's folder
Turning skills on or off, moving them and deleting them make and remove links, write the agents'
own settings files and move and delete skill folders, but took the orchestration operate scope.
They now take the filesystem write scope, as writing a project file does, and the Skills page's
switches follow it, since they read the same grant.
The git tracking check ran `git ls-files` in any absolute folder it was given. It now takes the
filesystem read scope, and the skill catalog's lookup that it goes through refuses a folder that
isn't a registered project's workspace root, like the list and a single skill do.
The skills MCP tools keep their own gate: reads are open to any caller, and changes need a live
full-access thread or a client approved above read-only, which is stricter than the scope.
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
0 commit comments