kosters.ai

For Keith · June 2026

Hermes Command Package

Everything below is built and running. This page is the visual walkthrough: your site, your overseer, and the same Command Deck surface I use daily. Screenshots are live captures from production, not mockups.

Executive summary

You spent a career making complex systems legible to other people. This package points the same instinct at your own time: one private overseer (Hermes), a toolkit of agents that work on free models by default, and a fixed home on the internet. The hard engineering is done. What remains is hardware (one Mac mini) and your say-so on outbound contact.

ComponentStatusNotes
kosters.ai Live Private landing page and setup guide. Domain held for transfer into your name.
Hermes overseer Live VPS instance watching your site and infra. Alerts intentionally muted until you enable them.
Command Deck Live Same dashboard as mine: topology, fleet, workstreams, supervision. Private Tailscale link from Zack.
White paper Live This page. Live screenshots updated as the package ships.
iMessage relay Live Mac relay up. Blue bubbles to your number when you enable alerts (not Zack's Sendblue line).
Voice surface Live Caller relay and Hermes TTS on the VPS. Surprise demo call already placed.
Agent fleet toolkit Ready ai-fleet on GitHub. Free models by default.
GitHub repos Pending Invites to hermes-keith and kosters-ai await your accept.
Domain transfer Pending Create Porkbun account kkoster with ID verification, then Zack pushes. Auth code ready as fallback.

Your site

kosters.ai is a private note: what is ready, the four-step path, and security boundaries in plain language. No theatre, no PII on the page.

kosters.ai landing page: You direct. The system does the work.
Figure 1 — kosters.ai overview. Brass accent, single column, built for easy scanning.
Setup guide with three pieces and four steps.
Figure 2 — Setup guide. Hermes, the agent fleet, and the machine ask.

Hermes Command Deck

This is the same Command Deck I run. Agent topology, live activity, fleet orchestration, workstreams, and supervision panels. It binds on Tailscale only; you open it with a private link after joining the tailnet (Zack sends the bookmark).

Hermes Command Deck main view with topology and live activity.
Figure 3 — Command Deck home. Ask bar, quick commands, live mesh, and activity stream.
Agent topology panel showing VPS, Hermes, Pi sentinel, and workers.
Figure 4 — Agent topology. VPS, relay, MCP fleet, Hermes core, Pi sentinel, watchdog, workers.
Fleet orchestration with agent teams.
Figure 5 — Fleet orchestration. Twenty agent teams, engine status, live orchestration graph.
Workstreams panel listing kosters.ai, Hermes, Mac mini handoff.
Figure 6 — Workstreams. Active lanes for site, overseer, handoff, and social connect.
Supervision and stewardship panels.
Figure 7 — Supervision. Stewardship rules, capability toggles, and deterministic watchdog.

Talking to Hermes (blue iMessage)

Short answer: Yes, Hermes can reach you on blue iMessage. Not through my Sendblue line (that one is mine). Yours routes through an iMessage relay on the Mac, so when alerts are on, messages arrive as real blue bubbles to your number.

Today: Outbound alerts are off by design. Nothing texts or calls until you flip that switch. The relay and voice surfaces are wired; they wait on your go.

Two-way orders: On my build, I text a Sendblue number and Hermes replies on-thread. On yours, the first path is relay outbound plus the Command Deck for commands. When your Mac mini is home, we can add a dedicated Sendblue line the same way if you want parity.

Security model

Your four steps

  1. One Mac mini (16 GB RAM or more). Sign in as yourself, leave it on.
  2. Move Hermes inbash deploy/install-mac.sh from the hermes-keith repo.
  3. Put the fleet to work — agents on free models; premium only when you choose.
  4. Point at what matters — your priorities and the people behind them.

What Zack sends separately

The setup is ready to hand over. The direction is yours.