Choose the scope of your menu-bar monitor

One strip of pixels, three different jobs

A menu-bar monitor earns its place by answering a question faster than opening a full application. The hard part is deciding which question. Status Trio, Stats, and Syrtis share a location on macOS, yet their documented workflows sit at three distinct depths. Status Trio asks whether the Mac is connected, charged, and audible. Stats asks what the machine is doing internally. Syrtis asks where coding-agent tokens and quota are going. Treating them as interchangeable because each displays compact indicators would miss the design boundary that makes each useful.

Status Trio is the newest of the three. Its upstream release history begins with stable v1.0.0 in September 2026. The project combines battery, Wi-Fi, and volume in one configurable symbol that can live in the menu bar, the Dock, or both. Opening its popover reveals nearby-network and link details, battery information, paired Bluetooth devices, and audio inputs or outputs. That makes it a status-and-control surface, not merely a decorative icon.

Glance: compress the everyday signals

The best Status Trio evaluation is mundane. Disconnect power, mute audio, change the output device, and move between strong and weak Wi-Fi. Check whether the combined icon remains readable without demanding attention. Then open the popover and confirm that the details you actually use are close at hand. The app can expose Bluetooth and Wi-Fi information, but macOS permissions and public platform interfaces define real boundaries. Network switching remains in System Settings, and some device or display controls depend on hardware support.

That narrow scope is an advantage when the goal is reducing clutter. One icon replaces several routine indicators, while deeper pages remain available on demand. It is less suitable when the question is why a fan accelerated, which process exhausted memory, or whether disk traffic has been climbing. For those questions, compression would hide the very evidence needed for diagnosis.

Diagnose: expose the machine underneath

Stats takes the broader route. Its upstream documentation lists CPU, GPU, memory, disk, network, battery, sensors, Bluetooth, and multiple clocks as separate monitoring areas. A practical trial should enable only the modules needed for a known investigation: watch memory pressure during a build, compare network traffic during a sync, or observe temperature and power while a sustained workload runs. The project explicitly notes that sensor and Bluetooth collection can cost energy, so adding every available widget is not automatically the most informative configuration.

Stats also documents optional remote monitoring. That can help with a Mac used as a workstation or service host, but it changes the trust model: account authorization, streaming, launch-at-login behavior, and network reachability now matter. Its fan-control feature is described as legacy and unmaintained, another reminder to distinguish observation from intervention. Use Stats when the menu bar should lead into investigation, and verify unusual readings against Activity Monitor or another independent tool before acting.

Account: follow work that the system monitor cannot name

Syrtis measures a different resource. It reads session logs already written by supported coding agents and organizes tokens, estimated costs, models, quotas, daily activity, and agent-level breakdowns in a local menu-bar dashboard. The upstream project says the core parsing and aggregation happen locally, with no Syrtis account or cloud synchronization required for the basic workflow. Its quota cards can use provider access, so those integrations deserve separate review.

An actual evaluation should compare one short agent session against the source log and the provider's own usage page. Then repeat with a second supported tool, a cached prompt, and a subscription quota window. This tests parser coverage and accounting assumptions instead of merely admiring a graph. Estimated cost depends on current pricing data; quota information depends on provider interfaces; log formats can change without Syrtis controlling them. It is an accounting lens, not an authoritative invoice.

Pick a question before picking an icon

A useful decision rule is simple:

• Choose Status Trio when battery, connectivity, and sound should collapse into one calm glance.
• Choose Stats when you need broad machine telemetry and are willing to tune polling and modules.
• Choose Syrtis when the resource under scrutiny is coding-agent usage rather than CPU or battery.

Running more than one can make sense because their scopes barely overlap, but menu-bar space and background work are still finite. Start with one concrete question, enable the smallest useful surface, and observe its energy, privacy, and permission costs. A good monitor reduces uncertainty; an overgrown collection of monitors simply relocates it to the top edge of the screen.