Hermes Agent Profile Builder
A web dashboard from Nous Research for composing a Hermes agent in one guided flow — the clearest UX instance yet of the wiki’s “agent = composition” thesis. It replaces “several CLI steps” with a visual builder over four building blocks, which are exactly the primitives this spoke tracks separately:
- Identity — name + description (the name becomes a shell-command alias) → the agent’s
SOUL.md. - Model & Provider — Nous Portal / OpenRouter / NVIDIA / OpenAI / custom OpenAI-compatible endpoints (llm-provider, cross-wiki).
- Built-in Skills — toggleable, per-profile, load on-demand (agent-skills, agentskills-spec) — one-click installs from a Skills Hub.
- MCP Servers — MCP integrations via HTTP URL or local stdio command, from a one-click MCP catalog with inline key prompts.
Mechanics
- Local-only dashboard at
http://127.0.0.1:9119(loopback by default) — the local-first posture shared with openhuman. - Writes standard
config.yaml/.env/SOUL.md; each profile keeps isolated memory, sessions, and state DBs (the per-agent agent-memory separation). - CLI ⇄ GUI parity — the dashboard’s output mirrors the CLI; both paths edit the same profile, so the GUI is progressive disclosure for humans without losing scriptability.
- Open-source:
pip install 'hermes-agent[web]'(the[web]extra on the base hermes-agent).
Why it matters here
It turns the abstract formula “skills × MCP = agency” (agentskills-spec + model-context-protocol) into a literal four-field form, and makes “agent-as-config” concrete — identity/model/skills/MCP as dashboard toggles, the demand-side echo of amazon-bedrock‘s “model choice becomes a config parameter.” So the wiki’s separate threads (skills, MCP, model selection, memory, identity) are now a single composition surface in one shipping product — sharpening the standardization-reach open question: the building blocks are stable enough to assemble in a GUI.
Quality note
Source tier T3 (MarkTechPost trade-press coverage of a vendor announcement). Higher-tier primary —
the Nous Research repo/docs (github.com/nousresearch/hermes-agent, the source for hermes-agent) —
would be T1; ingested per the soft gate with this weakness recorded. freshness: volatile (a fast-moving
product feature). Claims are the vendor’s, relayed by trade press.
Related
hermes-agent · agent-skills · agentskills-spec · model-context-protocol · agent-memory · amazon-bedrock · openhuman · llm-provider