NeoHtop 1.3: I added a menu-bar companion to my Rust/Tauri system monitor
Hey folks, I'm the developer of NeoHtop. It started as a way to learn Rust and Tauri by building something other than another todo app. I've just released 1.3.0, and the menu-bar companion is one of the bigger additions.
The idea is simple: click the ghost, check CPU, RAM, GPU, network and free storage, and get back to what you were doing. The overview also shows your five busiest processes. Click one and it opens that process's inspector in the main window.
Making it a second window raised a few less visible questions. Should each window collect its own readings? What happens when you pause one? Does closing Settings accidentally quit the monitor?
The main app and companion now read the same Rust-owned sample and history. Pause and refresh cadence are shared, and the companion stops polling while it's hidden. Closing the main window quits by default; keeping the app running in the tray is an explicit setting. Closing Settings or About leaves the monitor running, and Quit always exits.
The rest of the update includes process trees with combined CPU/RAM, native app icons, local-port search (:3000), GPU monitoring and detail views for the main resources. The frontend moved to shared shadcn-svelte components while keeping all 24 themes.
GPU collection was also a reminder that cross-platform doesn't mean every platform exposes the same readings. The app uses IORegistry on macOS, AMD sysfs/NVIDIA NVML on Linux, and NVML/DXGI inventory on Windows. Unsupported counters stay unavailable. Chart history is roughly two minutes in memory, and Linux tray behavior still varies by desktop.
It's free, MIT-licensed, and has official macOS, Linux and Windows downloads. No account required.
Downloads and screenshots: abdenasser.github.io
Source and v1.3.0 notes: github.com/Abdenasser/neohtop/releases/tag/v1.3.0
Privacy: official builds send a basic launch count and version without a persistent identifier. Extra feature usage is opt-in. Process names, commands, paths, searches and system readings stay local. Details: abdenasser.github.io
If you've built a tray-first Tauri app, I'd be interested in how you handle the handoff between the small overview and the main window. Feedback on the actual workflow is welcome too.
The menu-bar companion, captured on macOS. A process opens its inspector in the main window.
The main app in Catppuccin. Real system capture; readings are examples from one machine, not benchmarks.
2 points · 2 comments
[Self-promotion] NeoHtop 1.3 is out. I finally moved it to shadcn-svelte (and kept all 24 themes)
Hey everyone, I'm the developer of NeoHtop. A few of you might remember the little Rust/Tauri/Svelte system monitor I shared here a while ago.
On an earlier post, someone asked whether I was using shadcn. The answer then was no: it was custom Svelte components and CSS. I also said I'd probably use a UI library if I started again. Well, I finally did the migration for 1.3.0.
The part I wanted to get right was keeping the themes. People liked those, and I didn't want the update to turn every theme into the same dark dashboard. All 24 are still there. Their palettes now map to semantic tokens that the shared shadcn-svelte controls use across the app, settings and menu-bar companion.
There are a few things beyond the UI rebuild that I'm happy to have in this release:
• A process tree with combined CPU and RAM, so you can follow an app's children instead of adding up separate rows.
• Local-port search. Type :3000 and find what's holding that port.
• GPU readings and resource details with short chart histories.
• A menu-bar overview with your resources and busiest processes. Clicking a process takes you to its inspector.
The menu bar and main window use the same backend sample and share pause state. The charts hold roughly two minutes in memory. GPU support depends on the driver, and family RAM totals can double-count shared pages.
It's still free and MIT-licensed, with macOS, Linux and Windows builds. No account needed.
App, downloads and screenshots: abdenasser.github.io
Code and release notes: github.com/Abdenasser/neohtop/releases/tag/v1.3.0
One privacy detail worth being clear about: official builds send a basic launch count and version without a persistent identifier. Extra usage sharing is opt-in. Process names, commands, paths, searches and system readings stay local. Full details: abdenasser.github.io
If you used an older version, I'd like to know how this one feels. And if you've done a similar component migration, what did you find hardest to keep consistent?
NeoHtop 1.3 in Catppuccin. Real macOS capture; readings are examples, not benchmarks.
The menu-bar overview. Select a process to inspect it in the main app.
6 points · 2 comments
Mentions
NeoHtop 1.3: I added a menu-bar companion to my Rust/Tauri system monitor Hey folks, I'm the developer of NeoHtop. It started as a way to learn Rust and Tauri by building something other than another todo app. I've just released 1.3.0, and the menu-bar companion is one of the bigger additions. The idea is simple: click the ghost, check CPU, RAM, GPU, network and free storage, and get back to what you were doing. The overview also shows your five busiest processes. Click one and it opens that process's inspector in the main window. Making it a second window raised a few less visible questions. Should each window collect its own readings? What happens when you pause one? Does closing Settings accidentally quit the monitor? The main app and companion now read the same Rust-owned sample and history. Pause and refresh cadence are shared, and the companion stops polling while it's hidden. Closing the main window quits by default; keeping the app running in the tray is an explicit setting. Closing Settings or About leaves the monitor running, and Quit always exits. The rest of the update includes process trees with combined CPU/RAM, native app icons, local-port search (:3000), GPU monitoring and detail views for the main resources. The frontend moved to shared shadcn-svelte components while keeping all 24 themes. GPU collection was also a reminder that cross-platform doesn't mean every platform exposes the same readings. The app uses IORegistry on macOS, AMD sysfs/NVIDIA NVML on Linux, and NVML/DXGI inventory on Windows. Unsupported counters stay unavailable. Chart history is roughly two minutes in memory, and Linux tray behavior still varies by desktop. It's free, MIT-licensed, and has official macOS, Linux and Windows downloads. No account required. Downloads and screenshots: abdenasser.github.io Source and v1.3.0 notes: github.com/Abdenasser/neohtop/releases/tag/v1.3.0 Privacy: official builds send a basic launch count and version without a persistent identifier. Extra feature usage is opt-in. Process names, commands, paths, searches and system readings stay local. Details: abdenasser.github.io If you've built a tray-first Tauri app, I'd be interested in how you handle the handoff between the small overview and the main window. Feedback on the actual workflow is welcome too. The menu-bar companion, captured on macOS. A process opens its inspector in the main window. The main app in Catppuccin. Real system capture; readings are examples from one machine, not benchmarks.
[Self-promotion] NeoHtop 1.3 is out. I finally moved it to shadcn-svelte (and kept all 24 themes) Hey everyone, I'm the developer of NeoHtop. A few of you might remember the little Rust/Tauri/Svelte system monitor I shared here a while ago. On an earlier post, someone asked whether I was using shadcn. The answer then was no: it was custom Svelte components and CSS. I also said I'd probably use a UI library if I started again. Well, I finally did the migration for 1.3.0. The part I wanted to get right was keeping the themes. People liked those, and I didn't want the update to turn every theme into the same dark dashboard. All 24 are still there. Their palettes now map to semantic tokens that the shared shadcn-svelte controls use across the app, settings and menu-bar companion. There are a few things beyond the UI rebuild that I'm happy to have in this release: • A process tree with combined CPU and RAM, so you can follow an app's children instead of adding up separate rows. • Local-port search. Type :3000 and find what's holding that port. • GPU readings and resource details with short chart histories. • A menu-bar overview with your resources and busiest processes. Clicking a process takes you to its inspector. The menu bar and main window use the same backend sample and share pause state. The charts hold roughly two minutes in memory. GPU support depends on the driver, and family RAM totals can double-count shared pages. It's still free and MIT-licensed, with macOS, Linux and Windows builds. No account needed. App, downloads and screenshots: abdenasser.github.io Code and release notes: github.com/Abdenasser/neohtop/releases/tag/v1.3.0 One privacy detail worth being clear about: official builds send a basic launch count and version without a persistent identifier. Extra usage sharing is opt-in. Process names, commands, paths, searches and system readings stay local. Full details: abdenasser.github.io If you used an older version, I'd like to know how this one feels. And if you've done a similar component migration, what did you find hardest to keep consistent? NeoHtop 1.3 in Catppuccin. Real macOS capture; readings are examples, not benchmarks. The menu-bar overview. Select a process to inspect it in the main app.