Resource Status Bar adds lightweight VS Code status bar items for whole-machine CPU, memory, and optional GPU usage.
Version 0.0.4 introduces a shared local daemon for multi-window reuse, plus the compact bar rendering and refresh improvements from earlier releases.
Current CPU, memory, and optional GPU usage for the whole machine
Rolling peak values over the configured peak window
Theme-aware warning foreground when usage crosses the threshold
Per-metric visibility, ordering, alignment, and optional color overrides
GPU is disabled by default and uses a slower refresh interval when enabled
GPU falls back to N/A or can be hidden when utilization is unavailable
CPU, memory, and GPU keep contiguous priorities so they stay grouped in the status bar
Multiple local desktop VS Code windows share one metrics daemon instead of sampling independently
Settings
resourceStatusBar.refreshIntervalSeconds
resourceStatusBar.warningThreshold
resourceStatusBar.peakWindowSeconds
resourceStatusBar.showPeak
resourceStatusBar.displayMode
resourceStatusBar.barStyle
resourceStatusBar.alignment
resourceStatusBar.metricOrder
resourceStatusBar.percentPrecision
resourceStatusBar.cpu.enabled
resourceStatusBar.cpu.color
resourceStatusBar.memory.enabled
resourceStatusBar.memory.color
resourceStatusBar.gpu.enabled
resourceStatusBar.gpu.color
resourceStatusBar.gpu.hideWhenUnavailable
resourceStatusBar.gpu.refreshIntervalSeconds
Notes
CPU reflects whole-machine utilization.
On Windows, CPU percentages may not exactly match Task Manager because the underlying APIs use different sampling semantics.
GPU utilization depends on operating system support, drivers, and hardware telemetry.
On unsupported machines the GPU item remains visible and shows N/A by default, unless resourceStatusBar.gpu.hideWhenUnavailable is enabled.
Local Desktop Scope
This extension's shared-daemon mode is designed for local desktop VS Code only.
Remote SSH, WSL, Dev Containers, Codespaces, and browser-based VS Code are not part of this feature scope.
Shared Daemon Behavior
Multiple local VS Code windows share one metrics daemon.
The daemon exits about five seconds after the last VS Code window disconnects.
Opening a new local VS Code window reconnects to the existing daemon or starts a new one if needed.
