Showcase / Multi-Agent System
Kiki & the Agent Team
I didn't just adopt AI tools. I designed and deployed a personal AI engineering team: six named agents across career, QA, work, infrastructure, and portfolio work, all routing through a chief-of-staff agent and a shared file-based brain on my home server, with a template slot ready for the next domain.
What it is
An org chart, not a pile of prompts
Most people use AI as a single assistant they re-explain themselves to every session. I designed mine as a team. Each major domain has a dedicated agent that knows its files, codebase, or career context. A chief-of-staff agent, Kiki, coordinates them and owns the shared memory. I talk to one agent; the work routes to the right specialist and the context survives across sessions, devices, and even a change of model. It runs entirely on my own hardware with no paid hosting for the agent layer.
The team
One chief of staff, five specialists
Each specialist lives close to the domain it owns and follows a shared convention file so the agents interoperate. Kiki is the hub; the rest are spokes.
Every new agent is created from a shared template so it links back to Kiki and follows the same conventions, which means the team grows without re-architecting.
The shared brain
franzy-os, a file-based second brain
An OKF v0.1 markdown bundle with structured memory, runbooks, and life domains. Any LLM reads the same plain files; there is no proprietary memory format to lock into. It auto-commits and pushes to GitHub nightly at 23:00 SGT via cron on atlas, so it is designed to survive a full machine rebuild.
- OKF v0.1
- Markdown + YAML
- Model-agnostic
- Nightly auto-backup
The implementation arm
Cursor dispatch pipeline
dispatch-cursor.sh sends an implementation plan to a Cursor agent inside an isolated git worktree; artifacts are logged to .dispatch/STATUS.md, and up to two workers run in parallel. It uses my Cursor subscription rather than API tokens, which keeps AI coding cost separate and controlled. It never pushes or merges; I review every diff.
- Isolated worktrees
- Parallel workers
- Human reviews the diff