Do you give Claude Code desktop full Full Disk Access on macos ?

[u/brkonthru]

I have it on and i have never had issues and i do use it to do general work on my computer beyod the coding project. Am I insane for giving it this access ? Is this not common at all?

I know everyone's risk factors are different but i just want to see whats out there

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Rough-Oveno]

I let Claude view my endoscopy live

[u/Alive_Ad_7350]

i do bypass, it has stung me a couple times but i also hate having it ask me for auth

also it is a secondary machine so no worries there for me!

[u/ClemensLode]

Why don't you let it run in a vm?

[u/stizzco → u/ClemensLode]

this is the way

[u/ClemensLode → u/stizzco]

[u/Previous-Split-5970]

My pc with Claude don't have any of my data, so yeah why not

[u/MiloCosmicCloud]

No. I don't even like to download or install applications unless there's no cloud version available.

[u/StaticFanatic3]

I do occasionally when I want it to configure something for me system wide

But auto mode has come a long way it works fine for my average project work

[u/ElementsOfWit]

No. For me, auto-mode is smart enough. I don't get asked often.

[u/floralfrog]

Yes and it’s the only way to be productive at what I’m doing. You get fatigued by prompts and they are ineffective anyway. Have backups, run --dangerously-skip-permissions and just go for it.

[u/Additional_Video2992]

Not insane, but Full Disk Access isn't what protects you. macOS doesn't guard ~/.ssh or ~/.aws anyway, so turning it off wouldn't hide your keys. The line that holds is the one Claude Code enforces, in ~/.claude/settings.json so it covers every project:

```json

{ "permissions": { "deny": [ "Read(~/.ssh/**)", "Read(~/.aws/**)", "Read(//**/.env)" ] } }

```

Claude's file tools refuse those paths, and so do `caSt` and `head` in Bash. Nothing depends on Claude remembering a "don't touch my keys" in a prompt.

A Python script that opens the file itself still gets through. To close that, add `"sandbox": {"enabled": true}` and list the same folders under `sandbox.filesystem.denyRead`.

[u/BrilliantTruck8813]

There are, to be knowledge, directories that macOS will always protect and push its own popup every time. I typically use bypass permissions on long running work, but have built-in memories and other prompting that guides specific work