Hermes
Hermes (Nous Research) is an agent that runs on a server and answers through gateways such as Telegram and Slack, plus its CLI, TUI and desktop app.
- Plugin: log has a Hermes plugin, named
log, in this repo underhermesPlugin/.- One plugin: it used to be two, a portable
log(tools, skills) and a nativelogHooks(hooks), because Hermes loads a folder with aplugin.yamlas native and ignores itsplugin.json, only a portable package can declare an MCP server, and only a native plugin can register hooks (hermes_cli/plugins_discovery.py,plugins_loader.py; Portable Agent Plugins). Aconfig.yamlserver wins over a package's anyway, so log's MCP server now comes fromconfig.yamland the plugin is one native folder,hermesPlugin/. - Install: log itself first, with
logMcpon the PATH.log launch --setup(pick Hermes) copies the plugin into<Hermes home>/plugins/logwith the log install's path and removes an oldplugins/logHooksthat log wrote; thenhermes plugins enable logandhermes mcp add log --command logMcp --env "LOG_ACCOUNTS=${LOG_ACCOUNTS}". The Hermes home isHERMES_HOME, else~/.hermes, else%LOCALAPPDATA%\\hermeson Windows (LOG_HERMES_DIRoverrides all three). - After setup or update:
log setupandlog updatesay two things when they copy the plugin. The first time the Desktop half lands, switch log on in Hermes Settings > Plugins (a package's Desktop half ships switched off). Whendashboard/plugin_api.pychanged, restart the Hermes gateway (hermes gateway restart; when the gateway runs by hand, stop it and start it again), because the gateway mounts the plugin's routes once at start and restarting the app alone keeps the old ones. They also name a running gateway that started before the routes on disk changed. - What it adds: every log play as a
log:<play>skill (generated fromdocs/useCases/bybun run skills:build), log's GenUI tools and recipes, a read-only log tab in the dashboard and the Desktop half that draws blocks and views. - The router hook:
pre_llm_callrunsscripts/hooks/event.ts UserPromptSubmit --host hermeswith the message (andSessionStartfirst on a session's first turn) and returns{ "context": … }, cut to 7,500 characters per event. It finds log by itself:LOG_ROOT, then thelog_rootthatlog launch --setupwrites, then Bun's globalnode_modules/@listeningkit/log(BUN_INSTALLor~/.bun), then npm's global folders. Whenconfig.yamlhas nomcp_servers.log, it adds a line saying so with the command that fixes it. - What it doesn't do yet: it has no hosted option; the hook runs only where log is installed on the same machine as Hermes.
- One plugin: it used to be two, a portable
- Connects:
- Config:
mcp_serversin~/.hermes/config.yaml. A remote server takesurlandauth: oauth; Hermes handles registration, PKCE and refresh, and keeps tokens in~/.hermes/mcp-tokens/<server>.json. A local server takescommand. (Hermes: MCP, MCP config reference) - Tool names: Hermes names tools
mcp_<server>_<tool>, so log's tools appear asmcp_log_reportand so on. - Reloading: after a config change, run
/reload-mcp.
- Config:
- Draws MCP Apps: Hermes's MCP page doesn't mention MCP Apps or
ui://resources, and Hermes isn't in the support matrix. Treat it as text.- Views: in Hermes Desktop,
report's answer names a::logviewline that log's Desktop plugin draws as the view; Telegram and the CLI get it as text. - Show me the browser: for an account that is signed in already,
sessionsSignIn { account, open: true }opens its browser through the same gates, hidden (no window or taskbar entry), andbrowserViewstreams it into the chat. - Sign-in: in Hermes Desktop,
sessionsSignInopens the account's browser andbrowserView's answer names a::logbrowser{account="..."}line; the agent writes it on its own line and the Desktop plugin draws the live browser there, on the owner's machine too, so the owner signs in in the chat. Telegram and the CLI sign in in the log console; a streamed browser has no window of its own unlessLOG_BROWSER_WINDOW=visible.
- Views: in Hermes Desktop,
- Guidance:
- Prompt router: with the plugin enabled,
pre_llm_callnames the play before each model call. Without it the model routes each request withgetGuide({ ask: "<the owner's words>" })(asmcp_log_getGuide). - Server instructions: Hermes's MCP page doesn't mention them.
- Resources and prompts: Hermes does wrap a server's resources and prompts as tools (
list_resources,read_resource,list_prompts,get_prompt), so log'slog://agentsresource can be read. - What's left: guidance comes through the tool descriptions and
getGuide. - Skills: the plugin's skills are named
log:<skill>by Hermes. Whether Hermes loads them as Claude Code does isn't checked by running it.
- Prompt router: with the plugin enabled,
- Approvals: Hermes routes MCP form elicitation to its approval prompts, which show as buttons on Telegram and Slack. URL elicitation is declined as unsupported.