The ecosystem is the image. Five live departments around the HERMES core — mission badges, agent status and data routing update in real time. Hover a room for intel, click to enter.
● MiniMax — workforce● GPT — creative brain● Codex — engineering◍ Badge = open missions◌ Ring = live workspace state⌘K Command palette
◈ LIVE HQ STATE — SOURCE: 127.0.0.1:8766···
Departments
···
···
···
Automations
···
···
Snapshot
···
Gateway aus — lokal starten, dann prüfen mit: hermes status · Live-Modus funktioniert nur auf dem Mac (Gateway 127.0.0.1:8766), nicht über die VPS-URL.
◈ OPS RHYTHM — ONE-CLICK DAILY OPERATIONS
Open Missions
0
tasks awaiting execution
Workflow Runs
0
total pipeline executions
Onboarding
0%
infrastructure checklist complete
⚙ ENGINE ASSIGNMENT — WHO RUNS WHAT, AND WHERE
ENGINE · MINIMAX
The Workforce
High-volume routine operations at fractions of a cent. Routing, planning, daily rhythm, status logs.
AGENTS: HERMES · ATLAS
DEPLOYED: COMMAND CORE · PERSONAL OPS
COST TIER: MINIMAL — USE FREELY
ENGINE · GPT (CHATGPT)
The Brain
Creative intelligence and deep reasoning. World building, agent design, drafting, research synthesis.
AGENTS: GPT · ECHO · ORACLE
DEPLOYED: ARCHITECT SUITE · CONTENT · RESEARCH
COST TIER: PREMIUM — USE FOR QUALITY
ENGINE · CODEX
The Forge
Specialized coding intelligence. Scripts, automation, debugging, and safe terminal-command decoding.
AGENTS: CODEX
DEPLOYED: ENGINEERING BAY
COST TIER: TARGETED — USE FOR BUILDS
⬡ SECTOR 02 · DEPARTMENT OPERATIONS
Departments & Agents
Each department is staffed with a named agent and repeatable workflows. Activate an agent to load its system prompt into the Live Console, or copy its activation prompt into ChatGPT.
⬡ SECTOR 03 · MISSION LOG
Mission Log
The operational task board of your HQ. Assign missions to departments, set priority, execute, and clear. Everything is saved locally on this machine.
⬡ SECTOR 04 · LIVE OPERATIONS CONSOLE
Live Console
Route real requests to all three engines — MiniMax (workforce), GPT (creative brain), Codex (engineering). Select an agent; its engine and system prompt load automatically. Requires your own API key(s) in Settings — keys are stored only in this browser and sent only to openrouter.ai / api.openai.com.
Active Agent
Engine
—
Model override
Leave empty for auto: the engine tries its model candidates in order until one responds. IDs with a slash route via OpenRouter; IDs without route directly to OpenAI.
Session
Each agent's conversation is saved in this browser and reloads automatically — switch agents freely without losing context. Hover any reply to send it straight to the Mission Log. Clear wipes only the current agent's history.
0 / 40 messages stored for this agent
Cost principle: use the lightweight model for routine tasks. Reserve premium models for complex reasoning.
AGENT PROCESSING ▌
⬡ SECTOR 05 · PROMPT ARSENAL
Prompt Library
Every operational prompt from the Hermes system — world building, agent creation, workflows, and rescue protocols. One click to copy.
⬡ EMAIL OPERATIONS · LOCAL BRIDGE
📬 EmailOps
Read-only-Fenster auf dein lokales EmailOps-Command-Center (Inbox-Briefing, Antwort-Entwürfe, Aufräum-Plan). Läuft nur auf deinem eigenen Rechner — alle Aktionen (Senden, Aufräumen, Freigaben) bleiben bewusst im Terminal.
Live-Status · aus emailops-status.json
Noch keine Daten geladen.
Read-only. status.py im EmailOps-Ordner schreibt State/emailops-status.json — diese Datei hier laden oder aufs Panel ziehen. Ein Klick auf einen Entwurf kopiert seinen Pfad; Freigaben (APPROVED) passieren im Editor/Terminal, nie im Browser.
Live-Frontend (iframe)
📬 EmailOps: aus
Starte das EmailOps-Frontend lokal, dann öffne das Panel:
python3 dashboard.py im EmailOps-Ordner (Port 8765)
⚠ Diese Seite läuft über HTTPS. Der Browser blockiert den Zugriff auf das lokale
http://127.0.0.1:8765 (Mixed Content).
Das EmailOps-Panel funktioniert nur, wenn du diese HQ-Datei lokal öffnest
(per file:// oder lokalem Server).
Sicherheitsmodell: Das Panel ist ein sandboxed iframe (kein Senden, keine Formulare, keine Navigation). Credentials liegen ausschließlich im EmailOps-Backend, niemals im Browser.
⬡ SECTOR 06 · SYSTEM DIAGNOSTICS
System Status
Your 14-step infrastructure checklist from the Operator Onboarding, plus live HQ metrics. Click a step to mark it complete.
Infrastructure
0 / 14
onboarding steps complete
Agents Online
0 / 6
activated this session profile
Missions Cleared
0
completed all-time
Live Console — Tokens All-Time
0
in: 0 · out: 0 — cost detail in your OpenRouter dashboard
Console Requests
0
live requests routed through your engines
ONBOARDING PROGRESS
Data Control — Document Everything
Your entire HQ state (missions, notes, checklist, agent status and console conversations) lives in this browser. Export it regularly as a backup file into your HermesHQ/ folder.
HQ Folder Generator — Build Your Real Workspace
Generates a setup script that creates your complete HermesHQ/ folder structure — every department with its populated AGENTS.md and WORKFLOWS.md, plus a README. Save it into your home folder, then run: bash setup_hermes_hq.sh. Operator rule: let CODEX's Command Decoder verify it first — real operators always know what they're pasting.
Eight principles that govern how this HQ is built and run. Most AI users have chaos instead of infrastructure because they skip this. Read once. Internalize permanently.
◈ OVERWHELM PROTOCOL — RUN THIS WHEN LOST
01Slow down. You are not behind. There is no deadline — installation is the goal, not speed.
02Return to your agents. Describe exactly what you're stuck on and ask for a plain-language explanation. (Console → any agent, or the Rescue prompt in the Library.)
03Focus on one room only. One working department beats three half-built ones.
04Ignore advanced workflows. Build the core first — advanced comes after the foundation is solid.
05This feeling is normal. Every operator felt it. The ones who made it kept moving slowly forward.
◈ THE THREE RULES FOR EVERY INSTALL STEP
01Read the "what you should see" expectation before continuing. If output matches, you're good.
02Do not skip phases or run commands out of order. Each phase builds on the previous one.
03Slow is smooth. Smooth is fast. Read the explanation, then run the command.
ZERO PANIC MODE: You are not going to break anything. Your workspace profile is isolated. Credit is manual top-up only. And CODEX decodes every terminal command before you run it — use the Command Decoder workflow. Real operators always know what they're pasting.
⚙ Operator Settings
Stored only in this browser (localStorage) and sent exclusively to openrouter.ai when you use the Live Console. Never share it, never screenshot it. Create keys at openrouter.ai → Keys.
Optional direct line to GPT and Codex via api.openai.com. If empty, everything routes through OpenRouter with the key above — one key, all engines.
Model IDs change over time. Auto mode tries each candidate until one answers, so the console keeps working even when a provider renames a model. Check openrouter.ai/models for current IDs.
Manual tracker for your OpenRouter balance — shown in the topbar so cost stays visible. Verify real spend in your OpenRouter dashboard → Activity.
PRINCIPLE 03 — NEVER EXPOSE SECRETS. This key belongs in a password manager and here. It never goes in chat windows, screenshots, shared docs, or public repositories. Zero exceptions.
↑↓ navigateEnter executeEsc close⌘K / Ctrl K open anywhere
◈ Operator Manual — 60 Seconds
MAPHover rooms for live intel, click to enter. Badges show open missions. The Ops Rhythm buttons run your daily routine in one click.
FLOWFastest loop: ⌘K → type a workflow name → Enter. It opens the Console with the right agent + prompt preloaded. Fill the brackets, hit Send.
KEYS1–8 switch views · ⌘K/Ctrl K palette · ? this manual · Esc close anything
MISSIONSType in the palette anything that isn't a command — it becomes a "Log mission" action instantly.
LIVEOne OpenRouter key in ⚙ Settings powers all three engines. Every reply reports its model and token usage; totals accumulate in System Status.
BACKUPSystem Status → Export saves your entire HQ as JSON (keys excluded). The setup-script generator builds your real HermesHQ/ folder structure.
📬 EmailOps — Live (read-only)
Lädt http://127.0.0.1:8765. Bleibt leer, wenn EmailOps lokal nicht läuft — dann python3 dashboard.py starten.