A bridge for your systems
[!IMPORTANT] Any version 4 users will need to remove any integrations, and uninstall the old application before installing v5 to avoid conflicts. Your token and settings will not carry over to the new version.
A bridge for your systems.
[!NOTE] Contributions welcome! Feel free to submit a PR if you have any changes, fixes or improvements.
See installation documentation.
System Bridge reads most hardware metrics directly from the kernel, so these tools are not required. Installing them improves detection on some systems:
Linux
pciutils (lspci): resolves friendly GPU model names. GPUs are still
detected without it, but fall back to a generic name.lm_sensors: helps expose the full set of temperature and fan sensors on
some boards. Run sudo sensors-detect once to load the relevant modules.nvidia-utils (nvidia-smi): required for NVIDIA GPU metrics. Intel and
AMD GPUs use the kernel drm/hwmon interfaces and need nothing extra.Install with pacman (sudo pacman -S pciutils lm_sensors) or apt
(sudo apt install pciutils lm-sensors).
Windows / macOS: no optional tools are needed.
The system tray is enabled by default. Choose Hide system tray to hide it
after confirmation while the backend keeps running. To restore it, open the web
client's General Settings, enable System tray, save, and restart System
Bridge. The backend --no-tray flag overrides this setting.
On experimental macOS builds, hiding the icon also requires a restart.
Tray and Omarchy exit actions ask for confirmation before stopping System Bridge.
On Linux, these desktop prompts need zenity: install it with
sudo pacman -S zenity or sudo apt install zenity. Windows uses PowerShell and
macOS uses osascript, both included with the OS.
~/.local/share/system-bridge/v5/%LOCALAPPDATA%\system-bridge\v5\~/Library/Application Support/system-bridge/v5/~/.local/state/system-bridge/YYYY-MM-DD.log%LOCALAPPDATA%\system-bridge\logs\YYYY-MM-DD.log~/Library/Logs/system-bridge/YYYY-MM-DD.logSee the developing documentation for toolchain setup, build tasks, the pitchfork dev-server workflow, testing, and quality checks.
Quick start:
mise and run mise installmise run deps then mise run build:allmise run serve:all (Linux) or mise run run (all platforms)Allows other applications to connect to the backend. For example, in the Home Assistant integration.
No open issues yet, or sync has not completed.