Michael Williams
Private infrastructure · Historical case study
Bizzy Command Center was a private dashboard for a personal Mac-and-Windows fleet. This page preserves its former design and architecture; the dashboard is obsolete and does not describe the current setup.
In plain English
The former workflow brought scattered projects and AI tools into one private view. It was designed to reduce repeated remote-desktop setup and terminal context switching. The sections below document that historical design, rather than current capabilities.
Fleet control
The former design combined fleet health with project-aware session launch.
Conceptual view — no live operational data.
Archived studio window
The former public activity feed is retained only as historical context. Current fleet activity is not reported here.
Coarse and delayed by design. This surface cannot control the fleet.
Why it exists
Different projects, models, and services belong on different computers. That created a daily tax: check each machine, find the right folder, open the right terminal, and remember which session was still alive.
A small controller presents one dashboard while host-native agents keep execution on each machine. The interface coordinates the fleet; the files, credentials, tools, and compute stay where they already belong.
The everyday flow
The core interaction is deliberately short enough to use from a laptop, tablet, or phone.
Check availability, CPU, memory, disk, GPU, uptime, and the health of configured services.
Choose an online machine and a discovered project folder within its approved roots.
Launch Codex in that folder and optionally send the opening prompt with the session.
See managed sessions in one place and reattach without reconstructing the setup.
How it fits together
The browser never needs direct administrative access to each computer. The controller authenticates the person, polls the fleet, and proxies the approved session traffic.
A useful distinction
It makes a personal fleet legible and gives repeatable access to project-aware Codex sessions.
Codex and local services do the specialized work. The Command Center coordinates where that work runs.
Access stays on the private network; service actions are allowlisted, and session launches begin only inside approved project roots. The public artifact is this case study—not a live admin panel.
Design decisions
Because this interface sits close to real machines, the safety model is part of the product design.
The dashboard is intended for an encrypted personal network, with no public ingress.
Working directories are bounded and service actions are explicitly allowlisted.
Each host has its own identity; node credentials are not handed to the browser.
Selected privileged control-plane actions—such as session creation and stop events—are recorded in a local audit log with common secrets redacted.
Under the hood
The controller is a Python service with a compiled React interface and a local SQLite audit trail. Lightweight Python agents expose only the monitored state and allowed operations needed by the dashboard. Native pseudo-terminals keep command-line behavior correct across macOS and Windows.
Historical state
The case study documented version 0.3 of a private personal tool. That dashboard is now obsolete. Its prior feature descriptions remain here as historical design context, with no claim that the system is currently operational.
That is what the heck Bizzy Command Center is.
Explore the rest of the work