Claude now seems to forget that we allow "Do you trust the files in this folder?"
Status Closed — not planned
Maintainer reply ✓ Yes — wolffiex
Activity 11 comments · opened Jun 16, 2025 · closed Jan 7, 2026
💡 Likely answer: A maintainer (wolffiex, collaborator)
responded on this thread — see the highlighted reply below.
Every time that i start a new claude session in a previously approved folder, it will always ask to trust the folder. Is it possible to either fix this, or allow some mechanism to disable, or whitelist some folders?
11 Comments
Do you also get the prompt to set your theme? If so, we are mistakenly failing to load your settings. If not, we'll need to debug some more.
I do not have the theme situation going on. any debug logs I can give to you? ( it would be cool to permanently set some configs for this )
After a bit of messing around:
Yeah would like to know how to fix this for the home folder, often launch claude there when I just want to do some random things
I didn't have this issue before, but this has now become a reoccurring issue in v1.0.81 (I believe the first version this happened at was v1.0.77). For me, this only happens in subdirectories of my github root directory. For some reason, it does remember to trust the root directory project.
I suspect the reproduction steps here might be related to running
claudeinside a subdirectory (not at the Git repository root) combined with usingstatusline.For example, my setup looks like this:
When I launch
claudeinsidesub/, together withstatusline, I can reproduce the issue. Could this be the actual cause?settings.json:
Not using
statusLine, but I am using a subdirectory of my git repository, and I get this prompt on every Claude launch. Mine looks like this:My
settings.local.json:Facing the same issue on linux, its not asking me everytime on launch if i trust a folder unless i explicitly have a claude.md in that dir
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.