Omaspeedmeter

Omarchy bar widget showing CPU, memory, swap, network, temperature, GPU, and process count stats.

Click the widget in the bar to open a settings popup where you can toggle metrics, reorder segments, split network into up/down segments, switch icons for word labels, move the widget between bar sections, and change the refresh interval, GPU vendor, temperature source, and network interface — all without editing config files by hand. Right-click the widget to open a system monitor (btop by default, or htop).

Installation

omarchy plugin add https://github.com/mt-shihab26/omaspeedmeter.git --enable

To remove it:

omarchy plugin remove mt-shihab26.omaspeedmeter

See the Omarchy plugin manual for more on omarchy plugin commands.

Metrics

Each metric shows as a Nerd Font glyph icon by default, from the glyph set Omarchy already ships for the bar, so they render consistently with the built-in widgets. Enable word labels in the settings popup to show CPU, MEM, etc. instead.

CPU and network are rate-based and need two polls to produce a real number, so they show … for the first tick after the widget loads or after the refresh interval changes.

Settings

All settings are toggled/edited from the bar widget's click popup, and are persisted via omarchy bar set.

auto for GPU vendor and temperature zone probes the system on each poll; pinning a specific value skips detection and avoids picking the wrong sensor on machines with multiple thermal zones or GPUs. The network interface and temperature zone dropdowns are populated live from /sys/class/net and /sys/class/thermal when the popup opens.

The bar position dropdown (left/center/right) reads and writes the widget's placement via omarchy-shell/ omarchy bar move, independent of the defaultSection set on first install.

Each row in the popup's METRICS list has ▲/▼ buttons to move that metric up or down; the bar segments re-render in the new order immediately, and it persists the same way as every other setting. The ↺ button next to the popup title resets every setting in the table above back to its default, including the segment order.

Config file

Every setting above (plus the bar position) is also mirrored to a hand-editable JSON file at ~/.config/omaspeedmeter/config.json ($XDG_CONFIG_HOME/omaspeedmeter/config.json if set), kept in sync with the popup in both directions:

• Changing a setting in the popup updates the config file.
• Editing the config file (with the widget running) applies the change live — through the same path a popup click would use, so it also updates via omarchy bar set/omarchy bar move and stays consistent with the popup.

{
    "cpu": true,
    "mem": true,
    "swap": false,
    "net": true,
    "temp": false,
    "gpu": false,
    "procs": false,
    "labels": false,
    "netSplit": false,
    "interval": 2,
    "gap": 17,
    "gpuVendor": "auto",
    "tempZone": "auto",
    "netIface": "auto",
    "systemMonitor": "btop",
    "order": ["net", "cpu", "temp", "mem", "swap", "gpu", "procs"],
    "section": "right"
}

order and section accept the same values as the order setting and bar position dropdown above; unknown keys are ignored and missing keys keep their current value.

How it works

Each metric is collected by a small standalone bash script in bin/, run on a timer by BarWidget.qml and merged into a single stats object:

• omaspeedmeter-cpu — reads /proc/stat, diffs against a cached previous sample in $XDG_CACHE_HOME/omaspeedmeter/cpu to compute usage %.
• omaspeedmeter-mem — reads /proc/meminfo directly (no state needed).
• omaspeedmeter-swap — reads /proc/meminfo directly; emits null when no swap is configured.
• omaspeedmeter-net — reads interface byte counters from sysfs, diffs against $XDG_CACHE_HOME/omaspeedmeter/net to compute throughput.
• omaspeedmeter-temp — reads a thermal zone from sysfs, auto-preferring a zone whose type matches a known CPU sensor (coretemp, k10temp, etc.).
• omaspeedmeter-gpu — detects the GPU vendor and shells out to nvidia-smi, AMD's gpu_busy_percent sysfs file, or intel_gpu_top.
• omaspeedmeter-procs — counts /proc/[0-9]* directories.

Each script only runs when its metric is enabled, and only prints a single line of JSON (e.g. {"cpu":42}), which Model.js parses and formats into the bar segments. Model.js holds all the pure logic (settings resolution, formatting, segment building) separately from the QML so it can be reasoned about — and unit tested — without a Quickshell runtime.

Right-clicking the widget opens the configured systemMonitor (btop by default, or htop) via omarchy-launch-or-focus-tui, focusing an existing window for it instead of spawning a duplicate if one is already open.

~/.config/omaspeedmeter/config.json is watched with a Quickshell FileView, the same mechanism the Omarchy shell itself uses to hot-reload ~/.config/omarchy/shell.json. A change to either side — the popup or the file — is serialized through the same setSetting/setSection calls, so both stay consistent with each other and with omarchy bar set/omarchy bar move.

Requirements

• Linux with /proc and /sys available (standard on any distro).
• awk, bash, ip — present on virtually every system.
• GPU stats additionally require, depending on vendor:
  • NVIDIA: nvidia-smi
  • AMD: no extra tooling (reads sysfs directly)
  • Intel: intel_gpu_top and jq
• Right-click requires whichever systemMonitor is configured (btop or htop) to be installed.

If a required tool is missing, that metric's script emits null and the segment is skipped rather than erroring.

Project structure

.
├── .github/workflows/validate.yml  # CI: lint/format check on push and PR
├── CHANGELOG.md                    # notable changes per version
├── bin/                            # standalone stat-collector scripts, one per metric
│   ├── omaspeedmeter-cpu
│   ├── omaspeedmeter-gpu
│   ├── omaspeedmeter-mem
│   ├── omaspeedmeter-net
│   ├── omaspeedmeter-procs
│   ├── omaspeedmeter-swap
│   └── omaspeedmeter-temp
├── BarWidget.qml                   # bar segment UI, settings popup, polling timer
├── Model.js                        # pure logic: settings resolution, formatting, segments
├── manifest.json                   # Omarchy plugin manifest (id, defaults, settings schema)
├── format.sh                       # qmlformat + Prettier, run before committing
├── link.sh                         # symlinks the repo into ~/.config/omarchy/plugins
└── preview.png                     # screenshot used in this README

Development

git checkout dev

Development happens on dev. Run ./rebase.sh to keep it current with main: it pulls main, rebases dev onto it, and force-pushes dev.

./link.sh

Symlinks ~/.config/omarchy/plugins/omaspeedmeter to this repo, so Omarchy loads the plugin straight from your working tree instead of a copy. Run ./link.sh --remove to remove the symlink.

omarchy restart shell

Restarts the Omarchy shell to pick up changes (BarWidget.qml is not hot-reloaded).

./format.sh

Formats the repo: qmlformat for BarWidget.qml, Prettier for Markdown/JSON/JS. Run before committing.

Changelog

See CHANGELOG.md for notable changes per version.

License

This project is licensed under the MIT License.