3 ms·
Claude also checks your settings.json first, and if it sees a default there it then prefers that over anything in CLAUDE.md. This is particularly nefarious as t
by mitchitized 13d ago
Claude also checks your settings.json first, and if it sees a default there it then prefers that over anything in CLAUDE.md. This is particularly nefarious as they ship logic to presume a default if a setting is not there in settings.json, even if there are instructions in CLAUDE.md for exactly that.
For instance, say you added "do not add 'Made with Claude Code' in any issues, pull requests or wiki entries" in your CLAUDE.md. So far, so good.
Well the latest update now looks for something in your settings.json. Since you don't know about it, it is not set. Claude then says "not explicitly set, so now it is true by default". It completely ignores your CLAUDE.md.
Wait, what?
You shouldn't be shipping logic that arbitrarily redefines the behavior of the program, especially if your new logic actually ignores your own configuration or directives.
- combobyte 13d agoIt's almost like the whole thing is designed on vibes.
- tobyhinloopen 13d agoOooh so that is why it started doing that! I was so confused how it suddenly started writing that everywhere again
- springtimesun 13d agoI have this in a rules file. It respects it. The only thing that broke recently was when they added the session links. That needed an explicit additional rule. Sometimes rules don’t get added to worktrees but I haven’t had the patience to isolate why this only happens sometimes.
- sdf4j 12d agogot myself in a heated discussion with cc about that. It confessed that it added the ‘Made by Claude’ in a commit because a ‘mid session system-prompt refresh’ told it that, and that overwrites any previous instruction in CLAUDE.md