Cody HQ
A control room for a growing pile of small automations, designed like a game. A homestead map where every building is a project and every room is where the work happens.
Automations pile up. Visibility doesn't.
Every useful automation adds another script, schedule or workflow to keep track of. A few months in, nobody can say at a glance what's running, what failed and what it's costing.
Dashboards are the usual answer, but I wanted something I'd actually open every day. So I made it a place instead of a table.
Worlds inside worlds.
The top level is a homestead. Each building is one area of life or work, with a status that shows whether it's live, in progress or still on the roadmap. Step through a door and the view changes to an isometric interior, where that building's rooms and workers live.
Anything not built yet appears as a dark entry on the manifest. The roadmap is part of the interface, so you always see what exists and what's coming.
Design principle: the interface does the explaining. Status pills, a mailbox that gathers notifications, a night mode and a privacy toggle that hides amounts on screen. Small touches like these are what make a tool feel worth opening.
Boring on purpose, where it counts.
The map is playful. The plumbing under it is deliberately strict, because a tool that touches personal data earns trust through limits, not features.
Read-only by default. Agents read, summarize and flag. Anything that writes has to be declared in its own spec first, with the limits enforced in code and in the database, not just in good intentions.
Least privilege. The service that saves data can only touch its own tables, and an automated test suite proves what it cannot do.
No stored logins. Data arrives through exports I pull myself, so the system never holds credentials for outside accounts.
Minimal data out. Anything sent to an AI model is scrubbed first, and exactly what was sent is logged so it can be audited later.
Early, and honest about it.
Three buildings run on real data today: a ledger, a field notebook and a mailbox that fills itself from the system's own events, including a warning when a data feed goes stale. A fourth gives a read-only view of a separate project. The shared API that lets rooms save their own data is built, and the next buildings plug into it. It's a work in progress, so there are no outcome claims here, just the design and the decisions behind it.