[BUG] macOS repeatedly prompts for Desktop/Documents/Downloads folder access

[vpontis]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Claude Code triggers repeated macOS permission popups for protected folders (Desktop, Documents, Downloads) even after granting permission. The popup shows "1.0.112 would like to access files in your [folder] folder" and reappears every time Claude Code updates itself.

What Should Happen?

It should not be opening this prompt all of the time.

Error Messages/Logs

Steps to Reproduce

I'm not sure how to repro it - but I've seen it consistently on my computer.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

1.0.112

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

I'm using Ghostty.

[dicksontsai]

This happens when you run Claude Code from your home directory, which is not recommended. Consider making subdirectories so that you limit the file access of Claude and other automation in the agent loop.

[vpontis]

@dicksontsai thanks for getting back to me so quickly!

This happens when you run Claude Code from your home directory, which is not recommended. Consider making subdirectories so that you limit the file access of Claude and other automation in the agent loop.

I'm not running Claude Code from my home directory though. I'm in ~/Code/mono.

I'll poke around and see if there is some weird orphaned process but I basically never run Claude Code from my home directory so that doesn't seem to be the issue. Or if it is the issue, then maybe it's some issue with an editor like Zed or something like that which is doing something without my consent...

Looks like it might be related to zed-industries/zed#37620

[github-actions]

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.