So I've been having a nagging issue with my laptop: it has both an integrated Intel UHD 770 and a dedicated NVIDIA RTX A1000, and I suspected the system wasn't actually using the A1000 for anything. Instead of spending an hour googling, I decided to let Claude Code (Anthropic's CLI AI tool) walk through the diagnosis with me.
Here's the thing though, every single command it wanted to run got shown to me first, with a plain-English explanation of what it was doing and why. I approved or denied each one before it executed. Nothing ran silently in the background.
What it actually did, step by step:
1.
lspci | grep -i vga — Listed all GPU hardware on the PCI bus to confirm both GPUs were physically present.2.
glxinfo | grep "OpenGL renderer" — Checked which GPU was actually handling OpenGL rendering (spoiler: Intel, not NVIDIA).3.
nvidia-smi — Checked NVIDIA driver status, GPU temperature, power draw, and what processes were using the card. Only Xorg was on it, using 4MB.4.
lsmod | grep nvidia — Confirmed the NVIDIA kernel modules were loaded.5.
pacman -Qs nvidia — Listed installed NVIDIA packages to see what driver stack was in place.6.
cat /proc/cmdline — Checked kernel boot parameters (confirmed nvidia-drm.modeset=1 was already set correctly).7.
udevadm info /dev/dri/card1 and card2 — Identified which DRI device node corresponded to which GPU.8.
cat /etc/sddm.conf — Checked the display manager config for any GPU preferences.9.
echo $XDG_SESSION_TYPE — Confirmed I'm running KDE Plasma on Wayland, not X11.The diagnosis: The NVIDIA driver is installed and working fine. The issue is just how hybrid GPU laptops work on Linux, the display output is physically wired through the Intel chip, so by default KWin (the KDE compositor) uses Intel for everything. NVIDIA sits idle in "offload" mode unless you explicitly tell an app to use it.
The fix is either:
Install `nvidia-prime` and use `prime-run <app>` to launch specific apps on the NVIDIA GPU.
Or force KWin to use NVIDIA as the primary renderer by setting
KWIN_DRM_DEVICES=/dev/dri/card1 in /etc/environment.My question:
What do you all think about this workflow, giving an AI access to your whole system, but with a human-in-the-loop approval step for every command?
On one hand it's genuinely useful. It ran 9 targeted diagnostic commands, explained each one clearly, and gave me a well-reasoned diagnosis in maybe 5 minutes.
On the other hand, it did have read access to things like kernel parameters, installed packages, hardware IDs, and system config files. Even with approval gates, you're trusting the AI to be honest about what a command does before you run it. A malicious or hallucinating model could describe a command as benign when it isn't.
Is the approval-per-command model enough of a safeguard? Or is "AI with full system access, even supervised" a line you wouldn't cross? Curious where people draw the line.
https://redd.it/1tyv75o
@r_linux
