[BUG] Trust prompt reappears on every launch, but only for the home directory
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet (as a currently-open issue — see related closed issues below)
- [x] This is a single bug report
- [x] I am using the latest version of Claude Code
What's Wrong?
Running claude from the home directory (/home/<user>) shows the "Do you trust the files in this folder?" prompt on every single launch, even after repeatedly selecting "1. Yes, proceed". Running claude from a regular subfolder (e.g. ~/some-project) persists trust correctly after one approval.
Environment:
- OS: Ubuntu 26.04 under WSL2 (Windows 11)
- Claude Code version: 2.1.283
- Working directory:
/home/<user>(home directory)
What Should Happen?
Trust decision should persist after first confirmation, same as it does for non-home directories.
Steps to Reproduce
cd ~claude- Select "1. Yes, proceed"
- Exit cleanly with
/exit claudeagain from~- Trust prompt reappears
Repeating from a subfolder instead of ~ does not reproduce the issue — trust persists there as expected.
Additional Context
Inspected ~/.claude.json directly: for the home-directory entry under projects, hasTrustDialogAccepted stays false across sessions regardless of how many times "Yes, proceed" is selected, or whether the prior session exited cleanly (/exit) vs. the terminal being closed directly. Non-home project entries in the same file correctly flip to true after one approval and stay that way.
This matches reports in two related, now-closed/locked issues:
- #2147 ("Claude now seems to forget that we allow 'Do you trust the files in this folder?'") — a commenter there (balheru) found the same home-directory-specific pattern back in June 2025: works fine for subfolders, never persists for the home folder.
- #9256 (closed as duplicate of #2147)
Both were auto-closed for inactivity rather than fixed, and #2147 is now locked so I can't comment there directly — filing fresh per the bot's own suggestion.
Is this a regression?
Unclear — per #2147, this has been reported intermittently since at least mid-2025 and is still present in 2.1.283.