Local AI Lab --- Connecting Telegram to Your Local AI
Pairing a Telegram bot with OpenClaw, and the static IP change that silently killed the connection.
Longer writing, newest first. 39 in total, page 2 of 4.
Pairing a Telegram bot with OpenClaw, and the static IP change that silently killed the connection.
Wiring OpenClaw and Pi together across containers with a small HTTP bridge, single-flight queueing, and a shared-secret token.
What an AI gateway actually does, why I picked OpenClaw, and setting it up as the layer that makes local models reachable from my phone.
Setting up Pi as a local coding agent against a 27B model on llama-server, from a fresh container to a passing smoke test.
Why llama.cpp beat Ollama for this hardware, and building two llama-server containers: one on CUDA, one on ROCm.
A PaperMC Minecraft server in an LXC container on Proxmox for LAN play between two laptops, gotchas included.
The design decisions and hands-on build of a 3-node Proxmox cluster for local AI inference, homelab services, and a phone-reachable agent stack.
After a year of leaning on cloud AI for everything, why a local, always-on AI stack is the next step.
How I moved from @bilarikan.bsky.social to @bil.arikan.ca on Bluesky and Tangled, including the two attempts that failed.
Claude for Small Business makes being a connector inside Claude essential for SMB software, and puts those same products a step closer to being replaced.