I'm Peter Thairu Muigai — I go by thairux online. I graduated from Kabarak University with a degree in Computer Science, and I've spent most of my time since building the kind of tools I wanted to exist: automation-first, properly tested, and solving real problems rather than tutorial ones.
How I work
I'm what you'd call an AI-primary developer. Most of my day is spent working alongside AI coding assistants — but I'm the one who decides what gets built, reviews the output, and holds the architecture together. I don't accept code I haven't analyzed. Over time that led me to build my own infrastructure: a memory protocol that lets every AI tool I use share one persistent context, a desktop agent for my personal workflows, and a set of automation rules that keep all of it honest.
I'd rather ship something that actually works than iterate on something half-finished. No prototypes for the sake of prototypes. When I start building, I finish.
What I'm building now
Three things in parallel:
- A cross-agent memory protocol — an open standard that lets multiple AI coding assistants share one persistent memory. Your plans, decisions, and project context follow you across tools instead of resetting every session. Core engine, protocol server, and integrations across three agent platforms, all fully tested and in daily production use.
- A local AI life agent — a privacy-first desktop application that runs entirely on local models. It remembers everything, generates media, and manages personal workflows without a single cloud dependency. Electron, local LLM inference, media generation pipeline.
- Education at Pixel Academy — training as an assistant instructor, teaching children and teens robotics and AI fundamentals, and helping run the day-to-day operations of the academy.
What I care about
Tools that respect the user. I'd rather own my infrastructure than rent my workflow from a company that might not exist in five years. That's why the memory protocol is open by design, why the desktop agent runs locally, and why I keep asking "what happens to the user when this service dies" as a design question.
Beyond the screen
I'm based in Nakuru, Kenya. When I'm not building or teaching, I'm usually reading about distributed systems, game design, and the philosophy of artificial intelligence — or overthinking the design of my own portfolio.