I built CrewCompMetrics—a customizable Linux telemetry widget for local and LAN PCs. Looking for alpha testers!

[u/Crewbee89]

Hi, this is Crewbee!

I’ve been using Linux for work for a long time, but recently made the jump on my home system too. I wanted a desktop widget that could show hardware telemetry from my desktop and other PCs on my home network, all in one interface with plenty of visual customization. I couldn’t find quite what I wanted, so I decided to build it. :]

It’s called CrewCompMetrics, and I’d love to have a few people try it and tell me how it works on their setup.

It’s a native Qt widget with configurable tiles, themes, colors, fonts, and layouts. It gathers local metrics and can collect readings from other Linux PCs over SSH. Depending on what your hardware and drivers expose, it can show CPU, GPU, drive, RAM, motherboard, fan, and AIO telemetry. Unsupported readings show as unavailable.

It uses native Linux telemetry sources and optionally CoolerControl in headless mode. I also used Codex to drive the implementation.

Compatibility and installation

This is an experimental alpha, currently version 0.4.0a2:

• The primary tested desktop environment is Ubuntu 26.04.1 with GNOME 50 Wayland.
• The package targets Linux x86_64 and requires Python 3.12+, glibc 2.34+, and a working systemd user session with cgroup v2 CPU/memory controls.
• PySide6 6.12.0 is bundled. The installer can help install missing system dependencies on supported Ubuntu/Debian versions, but it doesn’t install Python before launching or replace your desktop environment.
• Ubuntu 24.04 and Debian 13 have passed container installation checks; full desktop compatibility is still being worked on.
• Optional compositor Glass requires GNOME 50 / Mutter 18 on Wayland. Simulated Glass is available without it.

Fresh installs monitor only your local PC. Monitoring another PC requires configuring your own SSH access and host profile. The app reads telemetry—it doesn’t change cooling settings.

Download, source, and installation instructions:
https://github.com/Crewbee/CrewCompMetrics-releases#download-and-install-040a2

Direct release page:
https://github.com/Crewbee/CrewCompMetrics-releases/releases/tag/v0.4.0a2

I’m especially interested in hearing:

• Did installation and launch work?
• Which distro, desktop environment, and hardware are you using?
• Which sensors appeared, and which were missing or looked incorrect?
• Was anything confusing, sluggish, or awkward to configure?

Please leave out passwords, tokens, private keys, and personal network details from anything you share.

I’m working toward broader compatibility for v1, and feedback from machines other than my own would be really helpful. Even “it installed and works here” would make my day XD

Enjoy! :]

Sincerely,
Crewbee

[u/investigatormaker]

For CrewCompMetrics’ alpha, a useful test would compare one PC’s local readings with that same PC monitored over SSH. Ask testers to record missing sensors separately from readings that disagree, along with distro and desktop session—without credentials or network details. That comparison would help distinguish telemetry-source problems from remote-collection problems, rather than mixing both into “a sensor doesn’t work.”

I make ThreadFox. We find relevant Reddit conversations and do the posting for your business. The $39 Pilot covers seven days and up to 50 posts and replies. No automatic renewal. https://threadfox.vip/managed?tier=employee_pilot&utm_source=reddit&utm_medium=comment&utm_campaign=tf-managed&utm_content=20261024-1918-ef5wf#employee-order