Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Local Qwen3.8 27B pointed to my local Silverbullet wiki coupled with a harness makes it so smart in my environment. It knows my network and homelab better than me. It can find things in an instant, troubleshoot problems on its own. Magic.


Yeah even qwen 3.5 9B on my VERY old RX 580 from 2017 can make sense of my homelab given a few crucial pointers in a agents.md. I think that's wild.


How do you deal with security issues? Up until now, I've only run agents on a separate machine on its own physical subnet. (Admittedly this is paranoid and I could probably run it on a VM.)

I would love to give a local-LLM agent full access to my (very modest) homelab, but can't trust it not to delete my files or do something crazy. Maybe giving it its own non-root username, and therefore read access, allowing diagnosis but not fixing. But even a non-root user can do some damage, or exfiltrate system info just by using curl.


I worry about this myself but find some solace and peace in my backup strategy. I treat the harness as a user and set permissive authorizations where needed. I even let it suggest why and which permissions it would need for specific items and note these down in the wiki as well. The idea is that the LLMs takes into consideration why it has the permissions it has and doesn't try and work around them.


what do you run and what in your homelab? if you dont mind responding

i just run a spare pc for browsing and screenshots with proxies.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: