Dispatch 108
Week ↗

Admin UIs ship, repo cleanup follows

Thursday was a delivery day. The headline is in ops-center, where Phase 1 of the critical admin UIs finally crossed the line. Local users, LiteLLM wiring, and auth config all landed together, and the numbers…

Commits
3
Systems
2
Read
1min
Product capture

Ops-Center — admin command dashboard.

Thursday was a delivery day. The headline is in ops-center, where Phase 1 of the critical admin UIs finally crossed the line. Local users, LiteLLM wiring, and auth config all landed together, and the numbers are honest: a big bump, 100,946 lines added against 1,490 removed, across 1,068 files. That kind of spread is a whole feature set taking shape.

The work had the usual shape. I was after a working admin surface so the team could manage users, model routing, and auth settings without touching config files directly. The backend had the plumbing, the frontend had the holes, and the gap between them is where the actual work lives. What shipped is a coherent set of screens and API hooks that cover the three pain points we keep circling back to. The supporting docs in the repo, the quick reference, the credential integration test report, the deployment checklist, all of it is there now instead of scattered across chat and whiteboards.

Before that landed, there was OAuth redirect and SSL to fix. That commit cleaned the surface hard, 189 lines added and nearly 7,000 removed across 903 files. A lot of cache artifacts and stale markers got swept out, the redirect chain got tightened, and the Docker setup stopped tripping over itself. I used that chance to trim the repo to what we actually need, not what accumulated while we were moving fast.

I was after a working admin surface so the team could manage users, model routing, and auth settings without touching config files directly.

The other commit for the day was smaller but important in the quiet way. A bump to use the published unicorn-npu-core v1.0.0 from GitHub in unicorn-amanuensis. Requirements locked down, no surprises. When a dependency release lands on a Thursday, you take it.

The day added up to a shipped admin layer, a cleaned up backend surface, and a dependency pin that stops the version drift. Not glamorous, but it is the kind of thing that lets the rest of the team stop guessing.

Also in the frame

Real product captures — click any to enlarge.

ops center
shared memory
ops center