Separate user settings from app-created settings
Status Fixed / completed
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 8 comments · opened Jul 30, 2025 · closed Aug 10, 2025
I use NixOS which makes ~/.claude/settings.json read only because of how the configuration is handled. I noticed in 1.0.64 you introduced a setting feedbackSurveyState which writes itself onto the settings.json file and will throw an error when it attempts a write on the file.
Can you please adjust your settings to separate user-driven settings from application-driven settings. This is a similar separation in Linux, how user-driven settings will often go into ~/.config while application-driven settings go into /.local/share.
This will also affect anybody who uses settings as dotfiles, although more insidiously as it won't error on them but your feedback state variable will be wiped every time they refresh their settings files.
8 Comments
This change is horrible. I have a dotfiles repo (managed with chezmoi) and I am constantly having to overwrite this file now because of the modifications.
This is forcing the vscode ide integration to drop the connection. Needs to be resolved asap.
I find the automatic changes to settings.json problematic. They create unwanted diffs in version-controlled environments.
A workaround for this to help people with dotfiles or Nix configurations is to add this to your settings:
This sets the last shown time to somewhere in the year 2035. Definitely not what they would probably want, but it will allow you to continue with your own settings until it changes!
They appear to have removed
feedbackSurveyStatefrom the configuration as of 1.0.66.I appreciate the update Fred. I found that the workaround you shared wasn't working for me; not sure why. Also unrelated but it's frustrating that the changelog.md isn't updated before they publish new versions of the software.
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
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.