– CONTENT LIBRARY
Content pipeline.
Open, preview and download real Markdown documents from the local agent content library.
LIVE · ORCHESTRATION LAYER
One orchestrator.
four specialists.
Hermes is coordinating Scout · Scribe · Reach · Dev — routing every task to gpt-5.5 or MiniMax-M3 by complexity.
h
CORE
OR
SC
DV
SB
RE
gateway · unknowntelegram · unknownsource pending
– ACTIVE MISSIONS
00
open on the board0 resolved
⌘
CPU -- · RAM -- · DISK --
live– FOCUS · ORCHESTRATOR
Orchestrator workload share
0
% OF TASKS
– TASKS RESOLVED · BY AGENT
All logged runs
0
0 ok
completion / total
– FLEET · ORCHESTRATOR + 4
Per-agent state & throughput
– BUILD
Owner board.
Local missions are loading from board.db.
FLEET · CONFIGURATION
Five agents.
one console.
Inspect each specialist, route them to the right model, and watch the heartbeat of the entire fleet in one place.
⌁ 0 tasks logged⌘ 0% avg success↗ 0% routed to fast
– TASK SUMMARY · 24H
Throughput across the specialist fleet
TOTAL TASKS
0
live local logs
AVG SUCCESS
0.0%
5-agent rolling avg
5 agents · 0 models
– MODEL ROUTING
Route each agent
to its best brain.
/ read-only live routing from /api/state.fleet and /api/state.models
– ACTIVITY HEATMAP · 7D · 24H
When the fleet is busiest, UTC
HOT
– TASK DISTRIBUTION
Share of total cycles
0%
No logged cycles yet.
– REAL HERMES CHAT
Chat command center.
Send a controlled message to a selected Hermes profile. Replies stream from the real /api/chat/send endpoint; empty states and errors stay visible instead of silently doing nothing.
– OWNER BOARD · LOCAL board.db
Owner Board (local).
This tab edits the project-local board.db only. It is not the shared Hermes kanban board, and it will not move kanban cards such as MC-01…MC-11.
ORBITAL OFFICE · LIVE AGENTS
Orchestrator soleil,
agents en orbite.
Dev, Scout, Scribe et Reach tournent autour du noyau. Les agents actifs s’allument en bleu.
◎ LIVE · working_agents + chat
– HERMES CRON SOURCE
Schedule.
Loading cron source…
– DASHBOARD DOCS
How Mission Control works.
Overview shows gateway health, fleet activity, routing and recent run telemetry.
Agents lists Orchestrator, Scout, Scribe, Reach and Dev with their codes, roles, load, model and latest task.
Surface label: this page is the custom Mission Control dashboard on local port 51763. The official Hermes dashboard is a separate surface on port 4860 when that service is running.
Tasks / Owner Board edits the local project board.db. It is deliberately separate from Hermes kanban, so local task actions do not mutate kanban cards.
Schedule reads Hermes cron from the source path displayed in that tab; cron actions are routed through the Hermes CLI after validating the current job id.
Office displays live presence from /api/state.working_agents; active cards glow blue only while a real Hermes chat subprocess is running.
Content shows real agent-created Markdown content from the project content library.