Hermes on WholeTech network
Agent harness · CLI first · dashboard second

Hermes is the traffic controller for your AI stack.

Claude writes and thinks well. Codex edits, verifies, and deploys well. Gemini is useful for Google-shaped research and ecosystem coverage. Hermes is the harness around them: sessions, tools, skills, providers, dashboards, messages, and repeatable workflows.

Maintained by the WholeTech network · based on the local Hermes CLI installed on this workstation · corrections welcome.

Local command: hermes Web UI: hermes dashboard · port 9119 Best use: orchestration, not prose
01 — Role

Do not make Hermes another chatbot

The useful mental model is boring: Hermes is the wrapper that decides what should happen next, which agent or tool should do it, what context is allowed in, and what result gets recorded. The assistants do the work. Hermes keeps the work from becoming a pile of untraceable one-off chats.

01

Route

Pick the right model, provider, profile, toolset, or session for the job instead of treating every task like a fresh blank chat.

providersfallbacksprofiles
02

Remember

Keep session history, checkpoints, skills, memory, and project context tied to the work instead of scattered across separate apps.

sessionsmemorycheckpoints
03

Operate

Run tools, scripts, webhooks, cron jobs, dashboards, message gateways, and MCP servers from one command surface.

toolsmcpcron
02 — Interfaces

Command line first, web UI when helpful

On this Mac, Hermes is installed as a command. The web dashboard exists, but the CLI is the natural harness for repeatable work: scripts, deploys, provider selection, session resume, one-shot prompts, and tool-gated workflows.

SurfaceCommandUse it for
Classic chathermes or hermes chatInteractive planning and agent work from the terminal.
One-shothermes -z "prompt"Scripts, cron jobs, pipes, and repeatable checks where only the final answer should print.
Resumehermes --resume SESSIONPick up an existing line of work without rebuilding context from memory.
TUIhermes --tuiA more app-like terminal interface when long sessions need structure.
Dashboardhermes dashboardWeb UI on port 9119 for visibility, sessions, status, and management.
03 — Website flow

A good Hermes workflow is procedural

For the WholeTech network, Hermes should behave like an assignment desk. It should know the domain, the intended outcome, which assistant should handle the next step, and what verification closes the loop.

A

Pick the target

Choose a site from ~/websites/<domain>/, read the current page, and write a short acceptance test before asking any model to create prose.

B

Ask Claude for taste

Use Claude for positioning, critique, structure, copy, and whether the page has a point of view.

C

Ask Codex to ship

Use Codex for file edits, HTML hygiene, no-script cleanup, SSH deployment, backups, ownership fixes, and live HTTP verification.

D

Record the result

Store the URL, backup path, changed files, verification output, and next recommended site so tomorrow starts cleanly.

04 — Stack

Claude, Codex, Gemini, Hermes: different jobs

ToolBest roleFailure modeHermes should do
ClaudeWriting, critique, concepts, careful long-form thinking.Can produce polished pages that still need operational verification.Use for direction, then hand off to Codex for implementation.
CodexWorkspace edits, shell commands, tests, deploys, code review, repeatable ops.Can over-focus on implementation before the editorial point is sharp.Give it concrete files, constraints, and verification steps.
GeminiGoogle ecosystem coverage, broad research, search/product context.Event-driven pages age fast and need source review.Use it for source gathering, then freeze facts with citations and dates.
HermesHarness, router, session manager, tool gateway, dashboard, workflow memory.Becomes noise if treated like another general chat app.Stay boring: route, log, resume, verify, repeat.
05 — Commands

The command surface is the product

$ hermes                         # interactive chat
$ hermes --tui                   # terminal UI
$ hermes -z "audit this site"       # scriptable one-shot
$ hermes --resume SESSION_ID      # continue prior work
$ hermes dashboard               # web UI, port 9119
$ hermes doctor                  # check setup
$ hermes sessions list           # inspect history
$ hermes mcp                     # MCP server management
Sharp take: Hermes becomes useful when it is allowed to be dull. The win is not a prettier chat box. The win is repeatable agent work with receipts.
06 — Rules

Operating rules for the harness

01

Every task gets an owner

Claude for concept, Codex for implementation, Gemini for Google facts, Hermes for orchestration. No mushy shared responsibility.

02

Every deploy gets a receipt

Live URL, HTTP status, backup path, changed file, and the command or agent session that made the change.

03

Every fact gets a date

AI product pages age quickly. If a claim depends on a launch, model name, price, or feature status, stamp it or cite it.