Description
When list_directory is called on a path that does not exist, it returns [DENIED] instead of an appropriate directory-not-found error.
Example call:
list_directory path=C:\Users\dries\Documents\Claude\Scheduled depth=2
Returns: [DENIED] Scheduled
The directory does not exist at all (confirmed via PowerShell Test-Path returning False). It is not an access/permissions issue -- the path simply is not there.
Expected behavior
Return a clear error indicating the directory does not exist, distinguishing it from an actual permissions denial.
Actual behavior
Returns [DENIED] Scheduled, which implies a permissions problem. This is misleading for both human users and LLM callers, who may then waste time investigating access rights when the real issue is a missing path.
Environment
- Desktop Commander v0.2.38
- Windows 11
- Node.js 25.7.0
Description
When list_directory is called on a path that does not exist, it returns [DENIED] instead of an appropriate directory-not-found error.
Example call:
list_directory path=C:\Users\dries\Documents\Claude\Scheduled depth=2Returns: [DENIED] Scheduled
The directory does not exist at all (confirmed via PowerShell Test-Path returning False). It is not an access/permissions issue -- the path simply is not there.
Expected behavior
Return a clear error indicating the directory does not exist, distinguishing it from an actual permissions denial.
Actual behavior
Returns [DENIED] Scheduled, which implies a permissions problem. This is misleading for both human users and LLM callers, who may then waste time investigating access rights when the real issue is a missing path.
Environment