Notice what needs attention
Watch for high CPU usage sustained over time. See the usage, observation window, and task runtime before interrupting legitimate work.
Sustained observation · Adjustable rulesSometimes the work is finished, but a process keeps running. QuietWatch spots sustained CPU usage, helps explain the task, and leaves the next step to you.

Local observationRules run on your Mac
Optional AI advicePreview before every request
You stay in controlConfirm every exit action
Turn a list of processes into useful context and a next step you can check.
Watch for high CPU usage sustained over time. See the usage, observation window, and task runtime before interrupting legitimate work.
Sustained observation · Adjustable rulesUse the process name, local path, and launch command to understand its origin. For another perspective, preview a summary and ask your AI service.
Task origin · Local assessment · Optional AICheck progress before waiting, muting, or requesting an exit. QuietWatch rechecks the target identity before acting and verifies the result afterward.
Confirmation · Identity checks · Follow-upFrom an overview to all processes and past actions. Clear in both light and dark.

Search, filter, and sort readable processes and their resource usage.
Actual app · Demonstration data
The app interface is currently in Chinese. Screenshots use sample data.
Close the main window and QuietWatch keeps observing from the menu bar. Check in when you need to, or pause observation while you focus on something else.
Process observation and rules run on your Mac. Local monitoring and actions work without an AI connection.
Read the full privacy noticeEach AI request shows its destination and exact summary before you confirm.
No raw commands, paths, PIDs, usernames, or project source code are sent.
API keys stay in macOS Keychain. Local event history can be exported or cleared.
No. QuietWatch shows the evidence and lets you choose whether to mute, request an exit, or force quit. Each exit action requires a separate confirmation. Force quitting may lose unsaved work.
Not necessarily. Builds, renders, and tests can legitimately use a lot of CPU. QuietWatch shows sustained usage, task origin, and observation time so you can check actual progress.
No. Monitoring, local rules, and process actions work locally. AI is optional and requires your own compatible service, model, and credentials. Provider charges may apply.
The universal package includes Intel and Apple Silicon binaries and requires macOS 13 or later. The app interface is currently in Chinese.
QuietWatch only shows processes readable by the current user. macOS limits access to some process information. You do not need to disable system security.
Open the DMG and drag QuietWatch into Applications. It is signed by JINGREN CHEN and notarized by Apple. To update, quit the old version and replace it with the new download. Updates are currently downloaded from this website.
Understand process CPU, whole-system idle capacity and accumulated CPU time, then use task progress to choose between waiting, quitting and force quitting.
Read guideIdentify which project, editor or script owns a busy node process before stopping it, and know when repeated high CPU calls for a performance profile.
Read guideCompare macOS Activity Monitor with QuietWatch fairly: immediate system-resource inspection versus sustained CPU alerts, task context and confirmed manual actions.
Read guideQuietWatch 1.0 is ready to download as a universal Mac app.
Open the DMG → Drag QuietWatch into Applications.