An all-in-one system monitoring and cleanup tool for developers.
Monitor CPU, memory, GPU, and disk in real time, then move into disk analysis, Docker cleanup, and process management from one app.
- Real-time monitoring: CPU, memory, GPU, and disk metrics with live charts
- Timeline: system health history, event timeline, point details, and alert intelligence (sustained alerts and recurring patterns)
- Alerts: configurable disk / memory / GPU usage alerts
- Disk analysis: folder scan, treemap, large files, extension breakdown, old file scan, recent growth, and duplicate detection
- Cleanup & automation: rule-based cleanup of cache / log / build / temp locations, a review inbox, and scheduled automated cleanup
- Docker management: inspect and clean up containers, images, volumes, and build cache
- Process tools: search, inspect, and terminate processes — including force-kill and whole process-tree termination
- Port tools: inspect active ports and monitor specific ports/IPs
- Developer tooling: environment health checks (Node, Python, Java, Docker, CUDA, PyTorch), toolchain cache cleanup, a port conflict center, project monitor, and workspace profiles
- Application cleanup: uninstall installed apps, review leftover app data, and clean leftover uninstall registry entries on Windows
- Growth tracking: snapshot-based folder growth analysis over 1 hour / 24 hours / 7 days
- Update checks: packaged builds can check for new releases and open the download page
- Localization: English / Korean UI
- Tray resident UX: restore the app from the menu bar or system tray
- Dark / light themes
For more detailed behavior, see docs/features.md.
| Page | Description |
|---|---|
| Overview | Live gauges, charts, alerts, storage summary, top consumers |
| Timeline | System health history, event timeline, point details, alert intelligence |
| Storage | Folder scan, treemap, large/old/duplicate file insights, recent growth, quick cleanup, file deletion |
| Docker | Containers / images / volumes / build cache management |
| Cleanup | Rule-based cleanup, preview, review inbox, and automation schedule/history |
| Activity | Processes, ports, and live port watch |
| DevTools | Dev environment health, dev servers, toolchain cache cleanup, port conflicts, project monitor, workspaces |
| Applications | Installed apps, related data cleanup, leftover data cleanup, Windows-only leftover registry cleanup |
| Preferences | Theme, language, alert thresholds, snapshot interval, update check, app data/log paths |
- Node.js
- npm
- macOS or Windows
Recommended:
- Node.js 24+
dockerCLI plus Docker Desktop or Docker Engine for Docker features- A standard Windows environment with
reg.exeavailable for Windows app management .nvmrcis included and pins the project to Node 24
# install dependencies
npm install
# development mode
npm run dev
# production build
npm run build
# preview built app
npm run previewSome features depend on OS tools or external commands.
- Docker pages require the
dockerCLI and a running Docker daemon. - Disk size measurement prefers
duon macOS/Linux and falls back to recursive scanning if unavailable. - APFS disk correction on macOS prefers
diskutiland falls back to standard filesystem information. - Windows app discovery uses
reg query.
Where possible, SystemScope degrades gracefully instead of failing hard when these commands are unavailable.
npm run dist:mac # macOS .dmg (Intel + Apple Silicon)
npm run dist:win # Windows .exenpm test # unit/integration tests
npm run test:watch
npm run build
npm run test:e2e # Electron + Playwright E2E (builds with --mode e2e, then runs)
npm run test:e2e:debug
npm run check # typecheck -> lint -> test -> buildE2E tests build the app first, then launch it through Playwright.
Recommended release flow:
npm run release:patch # or release:minor / release:major
git push origin main
git push origin --tagsThe release scripts run the full local validation flow first, then create the version commit and tag with npm version.
Pushing a v* tag triggers the release workflow, which builds platform artifacts and creates a draft GitHub Release.
src/
main/ Electron main process — IPC handlers and services grouped into domain packages (each with an index.ts barrel)
preload/ contextBridge API exposed to the renderer
renderer/ React UI — pages, feature modules, domain-grouped stores, and ui/layout components
shared/ IPC channels, shared types, constants, contracts
tests/
unit/ unit tests
integration/ integration tests
e2e/ Playwright-based Electron E2E tests
The renderer does not access Node APIs directly.
contextIsolation: truesandbox: truenodeIntegration: false- only explicit IPC APIs are exposed through
contextBridge - deletion paths are constrained and items are moved to Trash instead of being hard-deleted
- SystemScope supports both macOS and Windows.
- macOS includes APFS and unified-memory related corrections.
- Windows includes platform-specific handling for Quick Scan, app uninstall flows, Explorer opening, and tray behavior.
- Some system paths are intentionally restricted to open-only or trash-only flows for safety.
See docs/features.md for more platform-specific details.
Issues and pull requests are welcome. Before opening a PR, please make sure the full validation flow passes:
npm run check