Typical monitor
Shows that something is wrong.
- Raw CPU, memory, and disk readouts
- Little or no causal context
- User has to switch tools to investigate
SwiftBar Plugin For macOS Incident Triage
System Monitor turns load, memory pressure, disk, battery, and process spikes into one action-oriented menu: status, likely cause, next step, recent activity, and safe actions.
swiftbar/ subfoldermainWhy This Exists
This plugin tries to close the loop: detect a slowdown, preserve recent context, rank a likely cause, and put the next safe action nearby.
Typical monitor
System Monitor
Operational Model
The first screen answers three questions: what is wrong, what likely caused it, and what should happen next.
Lightweight history stays local in the plugin cache and compares current state with recent checkpoints before a slowdown.
Quick actions stay close to the diagnosis. More disruptive actions are explicitly separated so routine triage does not hide risk.
Semantic versions, release automation, workflow validation, docs, and a background updater are part of the product, not afterthoughts.
Install
swiftbar/ subfolder.chmod +x system-monitor.5s.sh once.About > Update from GitHub for updates.system-monitor.5s.sh from the latest release.brew install swiftbar
git clone https://github.com/oleg-koval/swiftbar-plugins.git
/path/to/swiftbar-plugins/swiftbar/
Open-Source Standards
Conventional Commits feed semantic-release, which updates the
changelog, syncs plugin version metadata, tags releases, and publishes the
script asset.
Plugin validation runs on macOS. The Pages site builds separately. Release revalidates before publishing so the shipped script matches the repo state.
View workflowsIssue forms, PR template, CODEOWNERS, security policy, Dependabot, and commit linting are wired in so outside contributions land cleanly.
Read contributing guide