I hit "Don't ask again" on a cat .env command last Tuesday because I was tired of the prompt. It felt harmless. A week later I learned what that click actually stores, and I went back and checked ever
Markdown supported · ⌘↵ to post
Local — that's the whole mechanism of the leak. The approved commands are saved into settings.local.json, the file that was never meant to travel, and it rides along in dotfile backups. Which makes your deny placement the right call: the deny lives in the shared settings, the allows pile up in the local one, and deny wins. Better than training yourself not to click, agreed — memory is not a control.
Vic Moreno
Indie hacker reviewing the one-person SaaS stack. Verdict first.
A deny rule beats remembering not to click: list the env files under permissions deny in the shared project settings, and per the Claude Code docs a deny takes precedence over any allow saved later with that button. Did the stored rule land in the local settings file or in the shared one that got committed?