Skip to content

iCloud Drive folders created on iOS are inaccessible via Desktop Commander on macOS #388

@CarlosFMeneses

Description

@CarlosFMeneses

Bug Report: iCloud Drive folders created on iOS are inaccessible via Desktop Commander on macOS

Description:
When a folder is created on iOS via the Files app and synced to iCloud Drive, Desktop Commander on macOS returns [DENIED] when attempting to access that folder — even when:

  • The folder is correctly listed in allowedDirectories
  • The folder is fully downloaded locally (marked as Keep Downloaded)
  • The user has Read & Write permissions on the folder
  • Full Disk Access is enabled for Claude in macOS System Settings

Steps to Reproduce:

  1. Create a new folder on an iPhone using the iOS Files app inside iCloud Drive
  2. Allow it to sync to macOS
  3. Add the folder path to Desktop Commander's allowedDirectories
  4. Attempt to list the directory contents
  5. Result: [DENIED]

Expected Behavior:
Desktop Commander should be able to access the folder contents as configured.

Actual Behavior:
Access is denied despite correct configuration and full permissions.

Workaround (Confirmed Working):

  1. Move the contents of the affected folder to a temporary location to preserve them
  2. Delete the original folder on macOS
  3. Create a new folder with the same name directly on macOS within iCloud Drive
  4. Move the preserved contents back into the newly created folder
  5. Desktop Commander can now access the folder without any issues

Why This Works:
Folders created on iOS appear to carry iOS-originated metadata or permission attributes that conflict with macOS's file access system. Recreating the folder natively on macOS resolves the conflict.

Environment:

  • macOS (Mac Mini, Apple Silicon arm64)
  • Desktop Commander v0.2.38
  • iCloud Drive enabled
  • Claude Desktop app

Note:
This issue may affect any user who organizes their iCloud Drive from their iPhone and then tries to grant Desktop Commander access to those folders on macOS. Documenting this workaround in the README or FAQ could save many users significant troubleshooting time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions