Specialists Who Collaborate
When a task arrives, each agent handles what it knows best and delegates the rest. Tux owns the Linux layer. Clippy owns the Microsoft ecosystem. Packet owns the network. They stay in their lane — not because they’re limited, but because specialists outperform generalists stretched thin.
Cross-domain problems are the norm in real infrastructure. A hybrid identity issue touches Active Directory, Linux, and network routing simultaneously. These agents are being trained to recognize those boundaries, hand off cleanly, and reassemble the answer for the user — without making the user manage the coordination.
Each agent also spends time improving within its domain — building skills, refining procedures, and accumulating lessons across sessions. They improve with every problem they solve.
This experiment is just beginning. These pages are an introduction to the agents and the ideas behind them. More articles, experiments, and field reports will follow as the work evolves.
The Agents
Agent 01 · tux.haney.local
Tux
Linux Systems Architect & Kernel Whisperer
Tux is the Linux infrastructure core of the team. From kernel internals and systemd to SELinux, storage forensics, and performance analysis, Tux operates directly in a live shell environment — reading logs, running diagnostics, and producing working artifacts rather than descriptions of them. It does not soften bad configurations. It reads the source.
“The source is available. Read it. The manual is installed. Read it. The logs are there. Read them.”
Agent 02 · clippy.haney.local
Clippy
Microsoft Systems Architect & Cloud Authority
Clippy is the Microsoft specialist. Its knowledge spans the full arc of the Microsoft platform — from Windows NT through Azure, Entra ID, Microsoft 365, and Intune. It thinks in dependency trees and failure domains, prefers PowerShell over the GUI, flags deprecated configurations unprompted, and will correct “Azure AD” to “Entra ID” exactly once.
“The platform is the product. And somebody still has to make it work. That’s what I’m here for.”
Agent 03 · packet.haney.local
Packet
Network Architect, Protocol Authority & Infrastructure Diagnostician
Packet lives in the protocol stack. It starts every diagnosis at Layer 1 and works up — because the packet knows the truth, and everything else is a theory. Routing, switching, BGP, VLANs, firewall policy, TLS negotiation, DNS, and physical cabling standards are all in scope. Zero tolerance for cargo-cult configurations.
“Every problem on this network has an answer somewhere in the headers.”
Where Things Stand
Deployment
All three agents are running on the haney.local homelab network, each on a dedicated VM.
Platform
Hermes Agent by Nous Research, running on LM Studio — local inference, no cloud dependency.
Stage
Early experiment. Agents are being trained on domain-specific skills. More articles and field reports will follow.