proctop

Live CPU and memory for the Omarchy bar: two braille history charts and a per-process table, in a panel under the bar item.

The bar carries a braille sparkline and percentage for CPU, the same for memory, and the 1, 5 and 15-minute load averages. Clicking it opens the panel:

• CPU, on an absolute 0–100% axis, and memory, framed on its own min–max band — against a 0–peak axis a flat memory series draws as a solid block and says nothing.
• A table of the ten largest processes with a CPU sparkline, its live CPU share, a memory sparkline and RSS. Click the heading to sort by CPU instead.
• Process, thread and running counts, plus load average.

Nothing polls. Samples arrive over yeet.graph.subscribe at 1 Hz, and the process list — the heavy one, every process with its stat each tick — drops to one sample every four seconds while the panel is shut, where the only thing reading it is the bar item's tooltip.

Every colour comes from the active Omarchy theme (muted → accent → urgent), so the panel follows whatever theme is set. On a deliberately monochrome theme there is no hue to follow and the charts render in greys.

Requirements

• yeet — yeet on PATH with yeetd running, and yeet login completed
• script from util-linux, which every Arch install has

The plugin runs one isolate — yeet run app.js under script, so it has a terminal — and talks to it over that process's stdin and stdout. No port is opened, and the isolate stops a few seconds after the last bar widget goes away.

Install

Add the plugin first. Until yeet is installed and its daemon running, the bar item shows what is missing and how to fix it:

omarchy plugin add https://github.com/yeet-src/omarchy-proctop --enable

Then run the pinned installer from the plugin checkout and log in. The installer fetches a fixed yeet release for your architecture, checks the package's sha256 and signature against values written in the script, installs it and starts the daemon:

sh ~/.config/omarchy/plugins/cx.yeet.proctop/install-yeet.sh
yeet login

To track new yeet releases along with the rest of the system, use the AUR package yeet-bin instead. It also pins a release and checks its sha256 and GPG signature before installing:

yay -S yeet-bin
sudo systemctl enable --now yeetd
yeet login

Other package managers are covered in the manual installation guide.

Remove

omarchy plugin remove cx.yeet.proctop

Building from source

The installable plugin is committed at the repository root — manifest.json, BarWidget.qml, Panel.qml, app.js and the vendored yeetkit/ runtime — so a clone is ready to load with no build step. The source of that output is app/page.jsx.

Rebuilding needs nothing outside this repository. The framework it is built with, yeetkit-omarchy, is committed as a packed tarball under vendor/, and package.json depends on that file:

npm install
npm run dist     # build into plugin/, then sync it to the root
npm run check    # drive the built plugin over a real portal

omarchy plugin validate . passes on a fresh clone, which is what omarchy plugin add produces. In a working tree it fails on node_modules/.bin/yeetkit-omarchy — npm always links a package's declared binary, and Omarchy allows no symlinks inside a plugin folder. node_modules/ is gitignored and never ships, so this affects only a tree you have installed into.

To move to a newer framework, check it out beside this repository and run npm run vendor, which re-packs it into vendor/ and reinstalls. Then npm run dist and commit the rebuilt root.

npm run dev builds straight into ~/.config/omarchy/plugins/cx.yeet.proctop and rebuilds on change. Note that the shell reloads app.js on its own, but picking up a change to the QML entry files needs omarchy restart shell.

Licence

Apache-2.0. See LICENSE.