Is anyone else having trouble with permissions when using NotePlan3 to manage your md files?
I switched over to using NotePlan3 to manage my md files from obsidian. All was peachy for a while but then about 2 days ago after an update to the Claude app, I am now getting a MacOS permission dialog (see screenshot) every time I run a skill that accesses the NotePlan3 files. " “claude” would like to access data from other apps. Keeping app data separate makes it easier to manage your privacy and security."
When troubleshooting this via Claude itself, I got several answers (of course) but the most believable was: " Matt, that popup is a separate macOS Sequoia permission — it’s not Full Disk Access. Apple added a new TCC prompt specifically for when one app reads data inside another app’s container directory. Your Cowork workspace is ~/Library/Containers/co.noteplan.NotePlan3/Data/... , which lives inside NotePlan’s sandbox container, so every time a skill touches that folder Claude trips the “access data from other apps” prompt."
I’d rather not click this literally every time I run a skill and I also do not want to move back to Obsidian. Any thoughts? Is anyone else encountering this? (I submitted a bug report to Anthropic).
I don’t think this is related to NotePlan because I have been experiencing the same issue for the past week or so, and it’s quite annoying. On top of “claude” I have the same pop-up where I’m prompted to allow “node”, too.
I’m seeing the same thing. Very annoying. I also reported the bug. If you have Keyboard Maestro, this Apple Script in a macro that runs every 1 second (periodic trigger) while Cowork is running will click the dialog for you. Makes the situation tolerable:
tell application "System Events"
tell process "UserNotificationCenter"
repeat with w in every window
try
if exists button "Allow" of w then
click button "Allow" of w
return "Clicked Allow"
end if
end try
end repeat
end tell
end tell
I had been using the Keyboard Maestro shortcut, which I had downloaded from Github I think some time ago … But now that shortcut isn’t working. I may have messed it up somehow. Can anyone look at the screenshot and spot anything that could be causing the trigger not to trigger? Thanks in advance!
Sandy
