Michael Williams
Private infrastructure · Operational
Bizzy Command Center turns a scattered Mac-and-Windows fleet into one understandable workspace. It shows which computers are ready, what capacity is available, and starts Codex on the machine that actually owns the project.
In plain English
My projects and AI tools do not all live on one machine. Instead of remembering where everything is, opening remote desktops, and rebuilding terminal context by hand, I choose a computer and project from one private page. The Command Center makes the connection, starts or resumes Codex there, and keeps the operational details out of the way.
Fleet control
Live health across the fleet, plus one direct path to start Codex where the work lives.
Conceptual view — no live operational data.
Public studio window
A delayed, read-only glimpse of aggregate fleet activity. It shows the shape of the work without exposing machines, addresses, ports, models, prompts, projects, or personal data.
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.
Current state
Version 0.3 adds a native, read-only iPhone dashboard and the privacy-filtered public studio window to fleet status, project discovery, managed Codex launch and reattachment, cross-platform terminals, service health, and audit logging. It is an operational personal tool, not a public SaaS product.
That is what the heck Bizzy Command Center is.
Explore the rest of the work