← Back to search

Claude Runs My Home Lab and Never Sees a Password

Human in the Loop: Two Ex-Microsoft Builders on AI · 2026-11-11 · 17 min
relevance 40 3426 words Episode page ↗ Audio ↗
Show full episode description
You are sitting in your own driveway, the garage door will not open, the automation that is supposed to see your phone coming has failed, and the CarPlay button that was the backup is not getting through on a weak 5G signal. So you text your roommate to open it. Except the roommate is Silas, an AI agent, and the door lifts seconds later through Home Assistant. That is what it looks like when a smart home grows past what one person can keep running: a dedicated firewall, a managed network with multiple VLANs, 65 containers on one mini PC, and a house full of people who expect all of it to just work. Chris walks through how he handed the upkeep to agents without handing over the keys. The lab splits into four layers - network, servers, apps and smart home - and the agents live on their own machine, a Mac mini that runs Claude Code and the Hermes agent. Two jobs run every night. At 3 AM the updater backs everything up and applies what it is trusted to apply: Home Assistant, firmware, Docker containers in Portainer. At 7 AM a Telegram report says what was detected, what was backed up, how the systems are doing and what needs his approval. It has run every night since May, and it started with only the safest tier of updates before it earned more. The rules are what make it work. Firewall rules, opened ports and DNS changes always wait for Chris. Day-to-day building happens in a dedicated Claude Code session in tmux and a Home Lab topic in Telegram, which is where Claude traced the Govee lights dropping off the network to a weak 2.4 GHz signal and turned the access point up. And no agent ever gets a password: every key lives in a dedicated 1Password vault, a /cred skill tells Claude or Silas which item to use, and a sync writes them to local files so nothing is ever pasted into a chat. The one time Chris did paste an API key, Claude told him to rotate it on the spot. Key takeaways: Split your home lab into layers (network, servers, apps, smart home) and give the agents their own machine instead of running them on the boxes they manage. Run updating and reporting as two separate jobs: a nightly updater that backs up first, and a morning report that tells you what changed and what needs approval. Start the agent on the safest tier of updates and widen it only after it has a track record. Trust is earned per kind of work. Write down what the agent never does on its own. Firewall rules, new open ports and DNS changes always wait for a human. Keep every credential in a password manager and point the agent at the item by name. If a key ever lands in a chat, rotate it. Watch the video version on YouTube · Full show notes, transcript + takeaways
✨ Episode Outline — click any point to jump to it in the episode
Problem solved
Maintaining a sprawling home lab and smart home (65+ containers, VLANs, firmware, certs) as a busy single dad by delegating upkeep to Claude Code and a Hermes agent named Silas.
Benefits
  • Nightly automated backups and updates across containers, Home Assistant and firmware
  • Daily 7am Telegram health report with items needing approval
  • Segmented VLANs keep IoT and kids' devices isolated from trusted gear
  • Claude now drafts firewall rules after earning trust over time
  • Agent never handles passwords; firewall, ports and DNS stay human-gated
Use cases
  • 3am job backs up and updates Home Assistant, WLED firmware, OPNsense and Portainer containers
  • Silas sends a 7am Telegram summary of what was detected, backed up and updated
  • Texting Silas to open the garage when CarPlay fails on poor 5G
  • Brightness sensor plus five time-of-day modes auto-manage living room lights for five years
  • Authelia SSO and reverse proxy expose docs/tv/zigbee subdomains on the home network only
KPIs / results
  • 65 containers on the home lab mini PC, 8 on the DNS PC
  • Nightly maintenance job running every single night since May
  • Certificates renewed every 90 days; Home Assistant updates monthly
  • Five VLANs: management, home, IoT, kids, guest
Tools / build
  • Silas (Hermes agent) on a Mac mini
  • The Grove (Claude Code second brain)
  • Home Assistant with OPNsense and TP-Link Omada
  • Portainer-managed Docker home lab
  • Authelia SSO behind a reverse proxy
  • Home lab research skill
0:00 / 0:00
So this started, right, like I said, single dad, I've got a great suburban house, unfinished basement, two floors, and over time it has evolved to smart lights, smart switches, smart garage door, smart locks. But then, well, smart everything. So this, it kept, it kept blowing up, right? So this started, my journey to today started a couple years ago where I was sitting on my couch one night and I got a notification from my router that a new device joined my network. And I got spooked. I got spooked. um, cause I'm like, man, what if, what if this random person has access to my budget spreadsheet that I just save on my machine because I've got no separation. I've got no VLANs. I've got nothing. So that kind of part of this multiple year journey that ends me up where I am today. So now I have a dedicated firewall. I have a prosumer, um, network, multiple switches. I've got network cable running through my walls and then I have a whole home lab with dozens of services. So, um, we'll kind of break that down here. So this started with, I literally have it. You can see 65 containers running on my home lab, mini PC, eight containers running on my DNS PC. And so that kind of turned into hell of its own, right? How do I maintain all of this setting it up as one thing, but now I have to make sure they're all up to date. Um, what if one of the containers dies? What if a light isn't responsive? What if certain parts of my network aren't getting good wifi coverage? What if my sort of my certs that I use for my shanku net that I have to have, you get it right. And now I'm managing it and I'm trying to be a dad and a full-time employee. Like, so what do we do when we want help? Managing anything technology related, Sash? Leash an agent. Unleash an agent. So that's what I kind of did. So how this kind of, to take a step back and look at it, I kind of break my home network, my smart home into four separate buckets. Network to the network is, again, I have a dedicated open, open, um, open sense is the software. It's the operating system, if you will, on a dedicated machine in my basement that hooks directly to my modem. And it goes out into, um, my Omada switch and Omada it's by TP link. That's the prosumer system that I use for my network. Three access points. I have multiple switches. I have DNS rules. I have multiple VLANs. And, uh, this is, this is my baby right here, man. This is my server in my basement. Yep. I've got my main switch right here. I've got it going into a patch panel to look clean. I have one, two, three raspberry pies. I have a Phillips hue bridge that you can't see here. I have a Lutron bridge and a car bridge. My one mini PC there. Anyway, it's crazy, man. I love it. Right. I've got airflow. I've got backup batteries, all of that. Um, so over time, more and more services came on. So I have a NAS to kind of manage like, um, a home streaming setup. I have a, I talked about my 14 or I have a network ride pie hole, um, to block ads. I have a, um, a docs app. I have, um, an app that takes an inventory of everything in my house. I have a reverse proxy. So I can go to things like docs. Shanku.org or tv. Shanku.org or zigbee. Shanku.org or home assistant. You get it. Um, and then of course I have the smart home sitting on top of that. But then the big introduction was with my Mac mini. Now I've got this AI box that hosts the Grove, right? Which is my Claude code. Second brain. It hosts Hermes agent, which is what Silas runs at. And now my dudes over there, they get to manage this for me. Yeah. And part of this is how I segregated my, my network. Right. So I have, um, I have a management VLAN that has no wifi access. This is ethernet only, and it just has all the critical devices to manage my network and run my machine. Right. Then I have my, what I call my home VLAN, which are all my trusted devices, my phone, my computers, but then also a lot of these servers, the ones that aren't crucial to running my network, right? Like my DNS, everything that sits on my management, but like my, my NAS home assistant, all that sits on my home VLAN. I have an IOT VLAN for untrusted devices and that IOT VLAN cannot interact with any other VLAN. It just can connect with the public internet. Then I have a kid's VLAN for my kids device, for my son's devices, my partner, Amanda and her kids devices that have stricter firewall rules on there that I can apply just to that. They can access certain sites as they get older. I can change that or I can block them, you know, screen times, all of that stuff. And then I have a guest, then I have a guest feeling as well. So it's been great, right? I can allow different, different forms. I have firewall rules that Claude now builds for me because it has proven its trust over time to let devices cross, right? Like I need my trusted devices on home to be able to communicate with my IOT devices on a different VLAN, but not the other way around. My printer, which is not a trusted device. I need that to show up on my home. When I want to do things like Apple air print because it only detect things. So a lot of things I've learned, same thing with Sonos, but it's great because now I can just rely on my agents to help me manage this problem that I have created that I love. It's crazy, man, that you ask about that. I loved Alexa so much when it first came out, right? I had it everywhere. I was using it. You know, I, I find myself not using it much these days and it has nothing to do like it. It'll, it'll work. It works. It, it, it set up on this. I think it was just, I don't know, man. I don't know what it was. There's no reason for it. It was so convenient. And one day I just stopped using it. That being said, there is a large part. So home assistant is the, the smart home operating system that I snapped to. It's a very open source. It's very private privacy focused. The idea of it is to manage it locally. So that we can use the devices that we buy without having to reach out to the public internet. Um, for instance, it's fantastic. I'd recommend it to anyone trying to manage a smart home. So they don't have to get locked into like only using Phillips. You were only using Govi or whatever. Right. Um, it is, is, it is amazing. Um, there's a large part of the home assistant community that has like almost like built their own voice sensors. People have created small voice ones off like simple ESP 32 chips so that they don't have to call up to Amazon service, right. Or Google or any of those. They're not listening to you. It's a, it's a privacy focusing. So at some point I might explore that. And I'd also love to, at some point, if there is local voice, can I just snap that into like Silas running on Hermes because Hermes supports voice now. Right. And just have that again, that's a, you got me thinking about that, but I don't, I don't use Alexa anymore, man. And so my goal with my smart home and I won't, I won't unpack that too much today, but my North star goal is I don't want to ever have to do anything. And it's sort of like how I think of AI, right? Like when I walk into a room, I want my smart home to know which room in my house that I'm in turn on the lights accordingly. And I've accomplished that in my downstairs living room. So over time, and we'll get to what's on the screen here over time, I have defined, I have five different times of day defined in my smart home based on sunset, based on brightness, based on when I go to bed, based on presence detection. And then I have different holidays as well. So for example, my living room downstairs, it's very open floor plan. It's a two floor living room, a two story living room. There's no floor right above it. So it's open. Gosh, there is so much natural light in that room. There's so much natural light. There's never a need to turn a light on during the day. So it's great. I have these systems based on time of day. However, what if it storms? All of a sudden, you need to turn on lights, except in the Shanku house, you don't have to worry about that because there is a brightness sensor that when it's during the day, when it's set to morning or day in the time of day for home assistant, but brightness dips below this automatically turn lights on. And as soon as brightness gets above it, if it stops warming, then the lights will cut off. It's fantastic. It works every time. I literally cannot tell you the last time that I've had to adjust lights in my living room. And this is going on now five years, but I want that kind of concept everywhere, right? Know what room I'm in, know what I need. If it's dark, turn the light on, et cetera. I doubt I'll get there because that's just kind of the goals that I set for myself, but that's the vision, right? So I would love to be able to talk to Hermes or talk to Silas to help on those instances where it's not. But for now, I at least have dashboards I can go to, or I can actually just message my agents directly. It's funny. It's funny. You say that about opening, opening the garage, Sash. Um, so that is a real life use case. So why, why I needed that. So I have a, um, I have an automation that when my, when my phone or when I leave my house, my garage door closes, when I get closed, it detects me. It opens my garage door. I also have a setting in Apple home, which is connected to home assistant, which is connected to my car, which runs CarPlay that also, as I get home in case my automation fails, I can tap a button on CarPlay. It'll open my garage. But then I got shit internet, shit 5g surrounding my house. So there have been times Sash and I'm just sitting in my driveway because my garage won't open. And even when I'm pressing the damn button on CarPlay, it won't open. So what do I do? Just feel like I'm back in college, man. Texting my roommate. Hey man, can you open the garage? Except this time my roommate is Silas, my agent. Come on open. The garage door just lifts up slowly. Right. It's like, I don't know if that's like the 40 year old walk of shame. Having to text your agent. Or that's just, that's just Chris Shanku's walk of shame right there. It is, it is pretty cool. I have, um, I now have my car programmed where I can press a button just in case. Right. But you know, I wonder if Silas misses that. Who knows, man? Who knows? So how I maintain this speak. So going back to my agent, my agents actually maintain my home lab for me. So there's two jobs that it runs. One is the 3am and that updates. Everything takes the backup of everything, um, goes through updates, everything home assistant and home assistant could be, you have to update the operating system itself or, um, a specific, like I use WLED to do some of the lights in my house. Each WLED device has a firmware update that I have to manage home assistant also can plug into open sense, my router manage updates there. So all of these devices on my network need to be updated with firmware. In addition, the applications that I run portainer, right. That's my UI for Docker. These Docker containers have updates. So it tracks all of this. It backs up everything. It initially I'll talk about this at the end. Initially I only had it doing updates for like my tier one things because some of the tier two, tier three smaller buckets were like on one. It was, could be untrusted updates from untrusted IOT manufacturers. Um, so over time that I have since kind of grown and gotten comfortable with that. Um, so what it does at 3am, it'll go through that, detect everything, back it up, then do the updates. It'll kind of document everything. And then at 7am I get a message on telegram from Silas. What is it that got detected? What is it that got backed up? It'll also give me a little health check. Um, how's my systems doing? Um, where does it, and then it'll ask me where I need action on like what it needs approval for me to do, et cetera. Um, that doesn't really show much, but yeah, so it's been, this has been running now. Um, you see on here, this has been running since May. Every single night, every single night, I get a report every morning of what it did. It started with what it needs to do, but you know how it is with AI, right? Like once, once I, once you have proven your trust, take the human out of the loop. I don't want to be involved. Just maintain it for me. Um, and this alone right here has saved me a ton of time having to manage all of this or just not manage it. Right. And now I'm four months without updates and how insecure, who knows? Yeah. It's been nice. Right. And this is kind of, as I've grown through this, um, part of that was starting with safe home assistant updates, starting it was, you know, backing up individual containers, read only checks. There are certain things. I think this, this list is actually outdated. Um, because I shouldn't say it's outdated. Um, OS updates and certificates is outdated because specifically for home assistant updates come out every month. Um, I want to renew my certificate every 90 days so that when I go to my, cause for all my apps, everything is behind, I use Othelia, which is a, um, an open source, um, single sign on that runs as a service. So everything kind of goes through that. I need to, I want to keep my certificate up to date so that I can go to things like docs.shanky.org or tv.shanky.org, which are only accessible for my home network without having to type, type in the IP address and the port and, and all of that stuff. So like anything, right. This is, this has grown over time, but there are certain things that it, it, it will not do on its own, right? Firewall rules, opening ports, DNS changes, all that. So that's been, that's been pretty nice, but like with anything, this kind of started off with doing random ad hoc requests. And then I start doing, I built some skills around this home lab research is one. Um, I have a dedicated, um, team up session, which I only have cloud code running. So it only has a dedicated home lab chat. I have a, um, inside telegram. I use groups in telegram. I have a dedicated topic in that group that is only for home lab. So I can interact, um, and just sort of a contained way. Um, and the skills are in there. There's, there's instructions, um, and commands to write, like ask me questions back to read the system, to do backups. Um, over time, it has really, really grown. And this is just a very simple home assistant dashboard that Claude one-shotted for me. It was like, Hey man, before I create this, I'm going to run through my traditional design things. You can improve designs. I'm like, I don't care. Just build it. And this is what I built. It's, it's not too bad, right? It's very simple. There's more to this, but like I can choose the time of day. I can choose, it knows whether I'm at home or not. But if I switched from Thanksgiving to Christmas or Halloween to Christmas, all of my lights respond accordingly, um, et cetera. But one, one cool thing on here that I, that I really, really liked was I have some, I have some Govi lights in my front yard. Lots of lights, man, lots of lights. And even though I have a really strong access point, the Govi lights themselves don't have strong wifi transmitters. And because Govi doesn't support, they don't support Zigbee, which is Zigbee is my, is my preferred smart home communication protocol. It has to go to wifi. There were devices that were just disconnecting from my, from my network. So I had Claude, you know, Hey, RCA this, what could be causing this? Um, it changed the setting, but it also realized that the closest access point in my house to that, the 2.4 gigahertz signal on that, it was sending off kind of a weak signal. And so it went ahead and increased that increased the frequency, increased the strength of that. And now that device doesn't drop anymore. And, uh, I wouldn't have fricking, I wouldn't have figured that out. Right. I wouldn't have known to look for that stuff. Like I'm not a network engineer. Yeah, man. Or just complained every time I had to manually do it. Right. And be annoyed. I know, I know. Um, so it just, it's been pretty nice. Right. So the big part of that though, of course, I talked about the beginning is like, I can't just give keys to Claude or church to Silas. Right. I did one time I gave a key to it. Cause I was like, Hey man, can you connect to this? And I don't have the way to connect. Here's my API key. It's like, bro, you need to, you need to cycle that key right now because that's persisted in chat. And you know, man, I'm sending these up to Anthropic or to open AI and I don't have local LMs running on my network yet. So I use everything. I use one password for all of my password management. So why not just bring that into my smart home as well? So now I have a dedicated one password vault that I can go in here and I can create all of these API keys, everything stored in here. And I have a cred skill that I can type slash cred, right. And tell Claude or Silas, Hey, this cred lives in one password. This is the name of it. Use that going forward. Right now I have this syncing back to local, local environment files on my machine. Um, because I'm restricted in one password by the number of interactions I can do per day. At some point I will justify bumping up and paying for the business plan because I don't want any of these files stored locally, right? It's great that one password can be the master and it will sink that down, right? If I need to go to a different machine or whatnot. Um, but ideally it'd be great to not have it in there. Regardless, Claude, Silas, any of my LLMs. They never actually get the key. Yeah.