7s

The landing. The Command Center clip, the one that counts, needs a signed-in session and comes next.

A task comes in, the agent acts, the operator approves.

  • RoleDesign, build, run
  • Ships320 since Sep 25 · last 19 d ago
  • DataThe public landing. The Command Center piece follows.

Notes

GalaxyCo · owned · Next.js · Postgres · Vercel · Sep 2026
Context

Agency work lives in six tools: chat, tasks, files, analytics, email, approvals. The operator spends the day switching between them.

Role

Design, build, run. Owned outright.

Approach

One operating system with an agent as a peer, not a chatbot. Floating sidebar, right drawer for detail, an agent dock that expands into a session with its own charts.

Solution

The Command Center: a task comes in, the agent acts, the result lands, the operator approves. One screen.

Result

The busiest repo in the workspace. 344 production deploys in three weeks.

Learned

Build for yourself first. Every screen was used the day it shipped.

Punch list · 3 open
  • Polish the Command Center conversation path
  • Film the one workflow
  • Approval gate on agent writes

This piece as markdown

Piece 5 of 6. Left and right arrow keys move between pieces.

ContactOklahoma City
© 2026 Dalton CoxEmail is the best way to reach me