Support
Start an analysis
Open Scavenger and choose Deep Analysis or Quick Cleanup. Launching the app does not start a scan. Quick Cleanup checks known cache locations in your authorized scope; Deep Analysis explores projects, local Agent history and storage. In a sandboxed build, select a location in the macOS permission panel. More → Scan scope lets you manage targets while analysis is stopped. Changing the scope clears previous results.
Permissions and missing results
Only accessible, authorized files can be analyzed. Canceling a first-time or expired authorization prompt does not start a scan. A root-folder selection does not grant unrestricted access to protected system files, other users, other app containers or other mounted volumes. Unreadable or unsupported locations are reported as incomplete; they are not treated as empty. If a saved location becomes unavailable, authorize it again through the system panel.
Understanding storage numbers
Logical file size, allocated storage and reclaimable space are different. APFS shared blocks, clones, compression and snapshots can change the relationship between file totals and disk usage. Results may be partial or change during a scan. Category ownership is inferred from paths and does not prove who created an item or that it is safe to remove.
Local AI-tool history
Scavenger can summarize supported local session metadata. It does not sign in to AI services, download cloud history or guarantee a complete conversation archive. Titles may include snippets saved by the original tool. Unsupported formats remain in storage totals with an explanation. A locally readable ChatGPT record does not by itself prove cloud synchronization is complete.
Review before cleanup
Select items, then review the exact full paths, measured sizes and action. In sandboxed builds, the system folder picker first grants temporary write access; that step does not clean anything. One subsequent cleanup confirmation is required each time, with Return set to cancel. Canceling either step leaves files in place. Supported dependencies, independently removable session records, reviewed app caches and logs use the system Trash. Disk-map context menus also allow explicitly choosing an eligible ordinary folder: this includes its entire contents, source code, Git history and personal files. This is a manual choice, not a judgment that the folder is junk. Shared databases and associated multi-file records remain managed by their original app. Moving to Trash does not immediately free disk space.
Direct cache deletion
A separate, clearly labeled action can permanently delete only these confirmed rebuildable cache locations under the current user: ~/Library/Caches/go-build, ~/.cache/go-build, and ModuleCache.noindex or SDKStatCaches.noindex directly within ~/Library/Developer/Xcode/DerivedData. It does not delete the entire DerivedData folder. You must review and confirm the exact list each time. This action bypasses Trash and cannot be undone. Quit related builds first. Scavenger never empties the Trash, executes package-manager commands or automatically cleans in the background. Measured allocation is an upper bound, not guaranteed released space.
Local settings and reset
Scan targets, directory authorization bookmarks and appearance preferences stay on your Mac. Remove a target to stop using it; an authorization shared by another target may remain until that target is removed too. Clearing all targets removes saved grants. The next Start Analysis begins the default selection flow again rather than creating a permanent exclusion list. This does not delete your files or change macOS privacy settings.
Report a problem
Contact orinoapp@163.com with the app version, macOS version, build type, the action you took and the visible error. Redact paths, project names, conversation titles and other private information from screenshots. Do not send credentials, full session databases or message contents. Developer: Zachari. App Store billing and download support, if applicable to your installation, is handled by Apple.