using @bot to manage a home lab running k3s with gitops is pure magic. Being able to leverage claude, codex, cursor, even antigravity while away from home with no direct connection to the home network and still have work done.
@NixFred@GrokBot Awesome, those are great wins!
I've been letting it configure my home network as well. I use pfsense and it has been surprisingly good at identifying traffic and making firewall rules.
I was able to continue improving the boot time of this device. Down to about 40 seconds. There's a little trick of loading from cache to save about 8-10 seconds while wi-fi initializes.
After having some quick success getting the digital frame setup like @wesbos with @grok@bot while I went out for errands.I wanted to make sure it was hardened properly. If you have the Allwinner A33 Model you'll want to read this thread.
Not a bad week, trying to use up the last bit of @claudeai tokens before the reset!
These repos benefited this week:
https://t.co/knYYc5ak4V
https://t.co/JbLe9bnOtb
https://t.co/LvkPdZoOxf
In addition to some local k3s configurations.
We did it! Framework Laptop 13 Pro is on TIME's Best Inventions of 2026. This is our third product to list, after the original Framework Laptop in 2021 and Framework Laptop 16 in 2023.
@NetworkChuck@bot@elonmusk@grok How'd you find the usage limit your first week?
I went too hard and used it all up in 2/3 days. Reset should be tomorrow, can't wait to get back to it and find a balance.
Additionally, the boot time has been reduced to just under 60s and we loaded a custom boot animation.
Once my @claudeai session limit resets I want to get back to trying to improve the boot time and work on pulling in the front doorbell camera feed
After having some quick success getting the digital frame setup like @wesbos with @grok@bot while I went out for errands.I wanted to make sure it was hardened properly. If you have the Allwinner A33 Model you'll want to read this thread.
Thankfully, the MAC is able to be pinned so only one MAC is used throughout the boot sequence and the device can receive the proper dhcp reservation and sync time correctly.
I put @claudeai on it to fix this issue. It noticed the MAC is random at boot (briefly) before wpa_supplicant came up. This meant there were 2 MACs for each boot. The main one and then this random one.
Thankfully I have NetAlertX running at home and kept noticing a new mac every time the frame was rebooted. Thankfully, this IP wasn't able to get out to the internet but it also wasn't able to reach my NTP server resulting in clock issues.