@OogieM posted about something similar to this before at Cannot Run Robot Assistant - #12 by OogieM
Her solution at that time was to create the vault in the “Public” folder. That’s a non-starter for me, because of what that folder is.
I’ve added the Filesystem connector, and given Claude permissions to that folder AND the folder one level above it. I’ve restarted Claude more times than I’d like to think about. Giving it access to my whole Documents folder is a non-starter.
What else should I be trying?
ETA: Google’s Gemini suggests I just give Claude “Full Disk Access”. Um…no. 
Me: Please try reading claude.md in the project folder
It looks like the file either doesn’t exist or there’s a permissions issue accessing it. Let me check what’s in the folder to get a clearer picture.
…
It seems there’s a permissions issue accessing the folder — the workspace can’t mount it right now. This might be a temporary glitch with your session’s folder access.A few things to try:
- Reload the session — close and reopen Cowork, then try again.
- Re-select the folder — if there’s an option to reconnect or reselect your workspace folder, that can reset the mount permissions.
- Check Obsidian is not locking the folder — if Obsidian has an exclusive lock on the vault, it might be blocking access.
If the issue persists, let me know and we can troubleshoot further!
Me: I’ve closed Obsidian. Please try again.
Still hitting the same error. The issue seems to be at the session level — the workspace environment can’t mount your folder at all, even with Obsidian closed. This isn’t a file-level permissions problem but rather something with how the current session is set up.
I’d recommend restarting Cowork entirely (quit and relaunch the app), then starting a fresh conversation. That should give the workspace a clean mount. If it still fails after that, it may be worth checking that the folder path hasn’t moved or that macOS hasn’t revoked Cowork’s disk access (you can check under System Settings → Privacy & Security → Files and Folders).