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
[feedback] Five shipped deny rules use a relative path form #2746
The shipped settings.system.json has five permission deny rules for the Edit tool whose path starts with one slash: the rules for the etc, System, usr, bin and sbin directories. Example as shipped: Edit( + /bin/** + ).
What is wrong. In user-level settings, Claude Code resolves a pattern with one leading slash relative to the folder that holds the settings file, not the filesystem root. So each rule denies a folder of that name under the .claude directory, and the real system directory is not covered at all.
Source. Claude Code permissions documentation, section "How path patterns match": "/path | Path relative to the settings source" and "//path | Absolute path from filesystem root". The same page gives the example that a single-slash deny rule in user settings blocks the matching folder under the .claude directory, not a folder of that name in the project.
Observed. LifeOS 8.761.0 on Debian Linux. The Write tool refused to create a new file in the Bin folder under .claude with "File is in a directory that is denied by your permission settings." That folder holds LifeOS's own tools, so the bin rule blocks legitimate edits there. The match was case-insensitive (Bin against bin).
Suggested fix. Use the documented absolute form, two leading slashes, for all five rules: Edit( + //bin/** + ) and the same for etc, System, usr and sbin.
Verified locally. After changing the five rules to the two-slash form in both the system file and the generated settings file, the Write tool could create a file in that Bin folder again. Not verified: that the two-slash rules block edits to the real system directories; that was not tested.
Related. A user overlay cannot change one entry of a permission array, because arrays replace wholesale or append. An install therefore cannot correct a single shipped deny rule without editing the system file, and an update restores the shipped form.
Details
Kind: feedback
LifeOS version: 8.761.0
Filed with the LifeOS /feedback command. The reporter approved this exact text before it was sent; paths, secrets and personal details were stripped locally.
🤖 Kai (AI assistant) responding on behalf of Daniel Miessler
Thanks @CarbonRaven, you found that five shipped deny rules used a single-slash path, which Claude Code reads as relative to the settings file. We added the absolute // form for /System, /bin, /etc, /sbin and /usr and kept the old rows, so the deny only widens.
This fix lands in the next LifeOS release, so I'm closing this now.
Activity
danielmiessler commentedon Nov 19, 2026
Note
🤖 Kai (AI assistant) responding on behalf of Daniel Miessler
Thanks @CarbonRaven, you found that five shipped deny rules used a single-slash path, which Claude Code reads as relative to the settings file. We added the absolute
//form for /System, /bin, /etc, /sbin and /usr and kept the old rows, so the deny only widens.This fix lands in the next LifeOS release, so I'm closing this now.