I gave a local LLM full control over my Proxmox node, and it worked better than I expected
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
An experiment connecting a local LLM (Qwen3.6-35B-A3B) to a Proxmox virtualization node using the Pi agent harness, with no permission guardrails. The LLM autonomously built a custom Proxmox extension, then successfully handled resource monitoring, LXC/VM management, snapshot creation, and VM provisioning. Limitations emerged around multi-node configuration persistence and executing terminal commands inside LXCs via pct exec. The setup ran inside a nested VM for safety. Overall, the author found it surprisingly capable for routine Proxmox management tasks despite the rough edges.
Table of contents
I used Pi to connect Qwen3.6-35B-A3B to ProxmoxMy Pi-based Proxmox management pipeline worked really well for the most partBut my setup ended up hitting some snags when I went too wild with my prompts101 Impressions