<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/i-gave-a-local-llm-full-control-over-my-proxmox-node-and-it-worked-better-than-i-expected-3hakdrs9o" -->

---
title: I gave a local LLM full control over my Proxmox node,...
description: 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...
canonical: https://daily.dev/posts/i-gave-a-local-llm-full-control-over-my-proxmox-node-and-it-worked-better-than-i-expected-3hakdrs9o
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: I gave a local LLM full control over my Proxmox node, and it worked better than I expected | daily.dev
og:description: 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...
og:url: https://daily.dev/posts/i-gave-a-local-llm-full-control-over-my-proxmox-node-and-it-worked-better-than-i-expected-3hakdrs9o
og:image: https://api.daily.dev/og/posts/3HAKDRs9o.png
og:image:alt: I gave a local LLM full control over my Proxmox node, and it worked better than I expected
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# I gave a local LLM full control over my Proxmox node, and it worked better than I expected

**[XDA Developers](https://daily.dev/sources/xda-developers)** · 7 min read · 1 upvotes · 0 comments

## Summary

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.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.xda-developers.com/i-gave-a-local-llm-full-control-of-my-proxmox-node>

## Questions this post answers

### Can a local LLM agent manage a Proxmox node without pre-set permission guardrails?

Yes, a Qwen3.6-35B-A3B model paired with the Pi agent harness successfully checked VM and container resource stats, listed container images, started and stopped LXCs, created snapshots, and even spun up a fully configured VM from a text description of CPU, memory, storage, and network needs, all without restrictive permission rules.

_daily.dev surfaces homelab experiments like this for developers weighing how far to trust local LLM agents with infrastructure._

### What goes wrong when using an LLM agent to run commands inside Proxmox LXC containers?

Attempting to have the agent run terminal commands inside LXCs via the pct exec command failed every single time despite the model recognizing the correct command, and each failed attempt triggered unwanted rewrites of the extension's config files, adding 5-10 minutes of wasted time before it gave up on the task.

_developers weighing LLM-driven ops tooling can track real failure modes like this via daily.dev before automating their own infrastructure._

### Why did an agent harness like Pi lose Proxmox node credentials after a restart?

Pi saved node credentials only in temporary session files rather than persisting them to the actual extension config, so restarting the Pi instance left the config empty and caused connection failures; the fix required manually re-running the /proxmox setup command to restore the node details.

_anyone automating server management with agent tools can follow gotchas like this on daily.dev before hitting them in production._

## Similar posts on daily.dev

- [I switched from Docker to Proxmox LXCs, and managing my home lab finally stopped being a chore](https://daily.dev/posts/i-switched-from-docker-to-proxmox-lxcs-and-managing-my-home-lab-finally-stopped-being-a-chore-vdkk6dlwb) · XDA Developers · 3 upvotes · 0 comments
- [I ditched cloud AI for a local LLM in Proxmox, and my home lab finally makes sense](https://daily.dev/posts/i-ditched-cloud-ai-for-a-local-llm-in-proxmox-and-my-home-lab-finally-makes-sense-bpysdey8n) · XDA Developers · 0 upvotes · 0 comments
- [Your Proxmox server can handle 10 times the workload if you stop treating everything like a virtual machine](https://daily.dev/posts/your-proxmox-server-can-handle-10-times-the-workload-if-you-stop-treating-everything-like-a-virtual--dlyllfspt) · XDA Developers · 1 upvotes · 0 comments
- [I ditched VMs for Linux containers, and my home server finally has room to breathe](https://daily.dev/posts/i-ditched-vms-for-linux-containers-and-my-home-server-finally-has-room-to-breathe-v6uh40yts) · XDA Developers · 2 upvotes · 0 comments

---

Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#mcp](https://daily.dev/tags/mcp), [#qwen](https://daily.dev/tags/qwen), [#proxmox](https://daily.dev/tags/proxmox)

[View this post on daily.dev](https://daily.dev/posts/i-gave-a-local-llm-full-control-over-my-proxmox-node-and-it-worked-better-than-i-expected-3hakdrs9o)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"I gave a local LLM full control over my Proxmox node, and it worked better than I expected","url":"https://daily.dev/posts/i-gave-a-local-llm-full-control-over-my-proxmox-node-and-it-worked-better-than-i-expected-3hakdrs9o","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/i-gave-a-local-llm-full-control-over-my-proxmox-node-and-it-worked-better-than-i-expected-3hakdrs9o"},"datePublished":"2026-07-02T13:03:41.809Z","dateModified":"2026-09-14T06:48:24.998Z","description":"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...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/41daa70b32c4c670da4a2abda8bc0252?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/41daa70b32c4c670da4a2abda8bc0252?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"XDA Developers","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"XDA Developers","logo":"https://media.daily.dev/image/upload/s--kCg6yyAP--/f_auto,q_auto/v1774964407/logos/xda-developers?_a=BAMAMiWQ0","url":"https://daily.dev/sources/xda-developers"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/i-gave-a-local-llm-full-control-over-my-proxmox-node-and-it-worked-better-than-i-expected-3hakdrs9o","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,mcp,qwen,proxmox","timeRequired":"PT7M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"XDA Developers","item":"https://daily.dev/sources/xda-developers"},{"@type":"ListItem","position":3,"name":"I gave a local LLM full control over my Proxmox node, and it worked better than I expected"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/i-gave-a-local-llm-full-control-over-my-proxmox-node-and-it-worked-better-than-i-expected-3hakdrs9o#faq","mainEntity":[{"@type":"Question","name":"Can a local LLM agent manage a Proxmox node without pre-set permission guardrails?","acceptedAnswer":{"@type":"Answer","text":"Yes, a Qwen3.6-35B-A3B model paired with the Pi agent harness successfully checked VM and container resource stats, listed container images, started and stopped LXCs, created snapshots, and even spun up a fully configured VM from a text description of CPU, memory, storage, and network needs, all without restrictive permission rules. daily.dev surfaces homelab experiments like this for developers weighing how far to trust local LLM agents with infrastructure."}},{"@type":"Question","name":"What goes wrong when using an LLM agent to run commands inside Proxmox LXC containers?","acceptedAnswer":{"@type":"Answer","text":"Attempting to have the agent run terminal commands inside LXCs via the pct exec command failed every single time despite the model recognizing the correct command, and each failed attempt triggered unwanted rewrites of the extension's config files, adding 5-10 minutes of wasted time before it gave up on the task. developers weighing LLM-driven ops tooling can track real failure modes like this via daily.dev before automating their own infrastructure."}},{"@type":"Question","name":"Why did an agent harness like Pi lose Proxmox node credentials after a restart?","acceptedAnswer":{"@type":"Answer","text":"Pi saved node credentials only in temporary session files rather than persisting them to the actual extension config, so restarting the Pi instance left the config empty and caused connection failures; the fix required manually re-running the /proxmox setup command to restore the node details. anyone automating server management with agent tools can follow gotchas like this on daily.dev before hitting them in production."}}]}
```

