Product Introduction
- Definition: Sluice is a native macOS utility and menu bar application specifically engineered for software developers and AI agent workflows to manage disk space by safely purging stale developer tool caches and build artifacts. Running natively on macOS 14 (Sonoma) or later for both Apple Silicon and Intel architectures, Sluice acts as an automated storage optimization engine tailored to engineering stacks.
- Core Value Proposition: Modern software development—especially when utilizing AI agents that spin up multiple concurrent development slots—rapidly exhausts local storage through hidden caches, simulators, and build leftovers. Sluice solves the "Mac disk full" problem by automatically detecting and flushing non-essential build data from tools like Xcode, Docker, Gradle, and EAS without ever interfering with active compilation processes.
Main Features
- Intelligent Developer Tool Scraping: Sluice automatically locates and evaluates cached data across a wide array of native and cross-platform developer ecosystems. It targets Xcode DerivedData, SwiftUI preview caches, stale iOS simulator runtimes and device debug support files, Docker and OrbStack build caches, untagged images, Gradle versions, EAS local build artifacts, and package manager caches including npm, Yarn, Bun, CocoaPods, Homebrew, SwiftPM, and pip.
- Process-Aware Safety Interlocks: To prevent corrupted builds or data loss, Sluice continuously monitors the active macOS process list. It refuses to initiate cleanup sequences if active compilation tasks—such as
xcodebuild, Gradle, EAS,docker build, Fastlane, or package installations—are currently executing. If a build process starts mid-cleanup, Sluice immediately halts operations. - Automated Scheduling and CLI Integration: Sluice Pro introduces automated nightly cleanups that catch up after Mac sleep cycles and triggers disk space preservation when free capacity drops below user-defined warning thresholds. Additionally, Sluice provides a command-line interface (CLI) with
status,check, andscancommands, allowing developers to embed storage validation directly into continuous integration or local release scripts (e.g.,sluice check --min 25G || sluice clean --yes).
Problems Solved
- Pain Point: Software engineers frequently encounter unexpected build failures due to depleted disk space caused by invisible gigabyte-scale accumulations of Xcode DerivedData, abandoned Docker build layers, and obsolete mobile simulator runtimes. Manual removal is tedious, risky, and requires deep familiarity with disparate file directory structures.
- Target Audience: iOS and macOS application developers, full-stack software engineers, mobile developers utilizing React Native or Expo (EAS), DevOps practitioners, and developers leveraging local AI coding agents that multiply containerized build environments.
- Use Cases: Preparing a resource-constrained MacBook for a massive production release build; reclaiming storage on a Mac mini running automated continuous integration pipelines; and managing local Docker container and OrbStack storage growth without accidentally deleting persistent database volumes or active project containers.
Unique Advantages
- Strengths & Limitations (Pros & Cons):
- Strengths: Deep domain-specific understanding of developer tool directories; process-safety locks that prevent race conditions during active builds; robust sandbox escape protection via strict path guardrails; low system footprint running directly from the macOS menu bar; and a helpful CLI utility for script-based pre-flight checks.
- Limitations: Automated scheduling and custom folder retention rules ("keep the newest N") require the paid Sluice Pro subscription (€19/year); the application is distributed outside the Mac App Store due to Apple sandbox limitations preventing direct access to third-party tool directories, requiring users to rely on direct download and manual notarization trust.
- Key Alternatives & Differentiation:
- CleanMyMac / DaisyDisk: General-purpose macOS storage cleaners excel at locating large media files and general system clutter, but they lack awareness of developer-specific dependency graphs, cannot detect running compilation processes, and risk deleting vital configuration caches. Sluice is purpose-built exclusively for developer ecosystems.
- Manual Shell Scripts: Many developers write custom cron jobs or terminal shell aliases to run
rm -rfon DerivedData or Docker system prunes. These manual or scripted approaches lack real-time process monitoring, often break active background builds, and do not provide automated low-space triggers or safety guardrails against path traversal errors.
Frequently Asked Questions (FAQ)
- Can Sluice delete my source code or important project data?
No. Sluice’s built-in developer categories exclusively target transient build artifacts, temporary files, and caches that are automatically regenerated by tools during the next build, pull, or package installation. Furthermore, built-in cleaning engines enforce strict path boundaries, refusing any operation that escapes designated directories via symlinks or parent directory traversal (
../). - How does Sluice differ from standard macOS disk cleaning utilities? Standard cleaners lack contextual awareness of software engineering toolchains. Sluice specifically understands where Xcode, Docker, Gradle, and package managers hide their data, safely calculates file staleness, and monitors the OS process tree to guarantee it never interrupts an ongoing build or deployment script.
- Does Sluice support Docker Desktop and OrbStack? Yes. Sluice seamlessly integrates with both Docker Desktop and OrbStack, targeting stale build caches and untagged images via official Docker CLI commands while strictly preserving persistent volumes and active containers.
- Is an internet connection required for Sluice to function? No. All file scanning, calculation, and deletion operations execute locally on your Mac. An internet connection is only utilized approximately once a week to verify Sluice Pro software license keys for subscribers.
