From desktop-manager
Diagnose a misbehaving hardware device — audio, display, USB, Bluetooth, network, input. Picks probe variants based on the machine profile (Wayland vs X11, pipewire vs pulseaudio, recorded GPU). Reads $CLAUDE_USER_DATA/desktop-manager/profile.json.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin desktop-managerTroubleshoot a hardware device on the local desktop. ## Prelude — load profile Read `desktop.session_type`, `desktop.audio_stack`, `hardware.gpu`, `quirks` from the profile. These shape which probes to run. ## Arguments `$ARGUMENTS` — the device class or symptom: `audio`, `display`, `usb`, `bluetooth`, `network`, `keyboard`, `mouse`, or a free-form description. ## Procedure 1. **Classify the issue**. If ambiguous, ask the user one clarifying question. Cross-reference `quirks` — if any quirk matches the symptom, surface it before running probes. 2. **Run the appropriate probe set**:...
Share bugs, ideas, or general feedback.
Troubleshoot a hardware device on the local desktop.
PLUGIN_DATA_DIR="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/desktop-manager"
PROFILE_FILE="$PLUGIN_DATA_DIR/profile.json"
if [ ! -f "$PROFILE_FILE" ]; then
echo "No machine profile found. Run /desktop-manager:onboard first."
exit 1
fi
Read desktop.session_type, desktop.audio_stack, hardware.gpu, quirks from the profile. These shape which probes to run.
$ARGUMENTS — the device class or symptom: audio, display, usb, bluetooth, network, keyboard, mouse, or a free-form description.
Classify the issue. If ambiguous, ask the user one clarifying question. Cross-reference quirks — if any quirk matches the symptom, surface it before running probes.
Run the appropriate probe set:
desktop.audio_stack:
pipewire → wpctl status, pactl info (pipewire-pulse shim), journalctl --user -u pipewire -u wireplumber -b --no-pager | tail -n 100.pulseaudio → pactl info, pactl list short sinks, pactl list short sources, journal for pulseaudio.alsa → aplay -l, arecord -l, dmesg | grep -i snd.desktop.session_type:
x11 → xrandr, glxinfo | head -n 20 if available.wayland → wlr-randr if available, else kscreen-doctor -o (KDE) / gnome-randr (GNOME).hardware.gpu[].driver_in_use against current lspci -k | grep -A2 VGA — flag drift.journalctl -b | grep -iE 'drm|gpu|nvidia|amdgpu|i915'.lsusb, dmesg --since "1 hour ago" | tail -n 100, recent journalctl -k.bluetoothctl show, systemctl status bluetooth, journal for bluetoothd.ip -br addr, ip route, nmcli device status, systemctl status NetworkManager, journal for NetworkManager.libinput list-devices (sudo), udevadm info for the device, journal for kernel input events.Summarise findings: device, kernel-visible?, daemon-managed?, error signatures in the log, any quirk matches.
Propose next steps ranked by invasiveness (restart daemon → reinstall driver → kernel module reload → reboot). Require confirmation before destructive action.
Write report to outputs/hw-triage-<class>-YYYY-MM-DD-HHMM.md (workspace) or $PLUGIN_DATA_DIR/reports/hw-triage-<class>-YYYY-MM-DD-HHMM.md.
If a recurring quirk is uncovered (something the user will keep tripping on), suggest /desktop-manager:update-profile quirks +"<short description>" so it gets recorded.