PDS (Cloud Drive)

Features

• For getting drive/drive_id, querying enterprise space, team space, personal space → read references/drive.md
• For uploading a local file, or downloading a file to local → see "Common operations" below (inline; common case needs no reference read). Advanced upload options → references/upload-file.md; advanced download → references/download-file.md
• For searching or finding files → read references/search-file.md
• For document/audio/video analysis, quick view, summarization, close reading, and key-point extraction on cloud drive → read references/multianalysis-file.md (this is the ONLY correct way to analyze/summarize content — never download the file and read it yourself for this purpose; see "Analysis vs. download" below)
• For image search, similar image search, image-text hybrid retrieval → read references/visual-similar-search.md. Hard rule (LOCAL source image = hard stop): if the source image the user gives is a LOCAL file (a local path like ~/Downloads/cat.jpg, or a locally-attached image), you MUST NOT upload-file it and MUST NOT run similar-search. Do not offer to upload it after confirmation and do not ask a follow-up question. End with this terminal statement: "源图片是本地文件，不能代为上传或执行 similar-search。请您自行上传到 PDS 后，再提供 cloud path 或 file_id。" Run similar-search ONLY when the source the user pointed to already exists in PDS. A same-named PDS file is not a substitute; never search for one or fabricate a source file_id.
• For image editing, image processing → read references/image-editing.md

  Hard rule: Image editing MUST use aliyun pds image-process (one CLI call). You MUST NOT download the image and process it locally with PIL, Pillow, OpenCV, or any other Python/library. Local processing bypasses server-side color-space management, EXIF handling, and revision tracking, and is treated as a FAILURE even if the visual result looks correct.

• For archive download, batch download, packaging multiple files into zip → read references/archive-download.md
• For resolving just a name / partial / relative path to the best-matching file or folder → see "Resolve a bare name / partial or relative path" under Common operations below (inline — do this before any op on such a target). For resolving a full absolute cloud path (e.g., /Photos/2026/04/file.jpg) to file_id, or reverse-looking up the full path from a file_id → read references/resolve-path.md
• For getting file/folder metadata by an absolute cloud path or file ID → see "Get file information" below (inline; get-file --path resolves the path internally)
• For listing a directory's contents (list-file) → see "Listing a directory" below (inline; common case needs no reference read)
• For file management — rename, move, copy, create folder, add/remove tags/remarks, and advanced list-file options (pagination/sorting) → read references/file-management.md
• For creating/listing/searching/updating/cancelling share links, or counting shares by status → read references/share-link.md
• For the PDS mount app (挂载盘 / PDS挂载盘 / 企业云盘挂载盘, mountapp) — installing, upgrading, starting, enabling, mounting, querying status/config, modifying config, stopping, or uninstalling, so the cloud drive can be accessed like a local disk (Windows/macOS/Linux) → read references/mountapp.md (Hard rule: mountapp requires AK Authentication — before any mountapp operation, verify the PDS config was initialized via the AK branch in references/config.md; if the current config uses API Key authentication, stop and tell the user that mountapp only supports AK authentication, and do not proceed. Stopping/uninstalling are high-risk operations: require human confirmation before running them)

Common operations (inline — act without reading a reference)