Hermes Agent adds ComfyUI skill with `/comfyui` workflow installs and local/cloud control

• NousResearch's launch post said Hermes Agent can now install, launch, manage, and run ComfyUI workflows on demand, turning a previously manual node pipeline into an agent-managed one.
• According to Teknium's command note, the skill is built in now: update Hermes with hermes update, then run /comfyui to start using it.
• ComfyUI's own post framed the integration in two directions at once: creators can describe the output they want, while developers get the broader Comfy ecosystem as a callable surface.
• The official Skills Hub says the comfyui skill handles image, video, and audio workflows, uses comfy-cli for install and lifecycle management, and executes jobs through ComfyUI's REST and WebSocket APIs.

You can browse the skill in the Hermes repo, check the official Skills Hub entry, and see that Hermes documents installed skills as dynamic slash commands in its slash command reference. NousResearch's demo post also shipped with a 40-second video of the flow, while ComfyUI's follow-up pointed people toward Comfy Hub for workflow discovery.

The new user-facing hook is simple. Teknium said users can update Hermes and run /comfyui, and Hermes docs say bundled or installed skills surface as slash commands.

That matters because ComfyUI usually starts as a separate toolchain. Here, the command becomes the entry point for installing, launching, and operating workflows from inside the agent session instead of bouncing out to a separate UI or terminal process.

The official Skills Hub describes comfyui as a built-in skill for generating images, video, and audio. Its responsibilities break down cleanly:

• install and launch ComfyUI
• manage nodes and models
• run workflows with parameter injection
• use comfy-cli for lifecycle operations
• use direct REST and WebSocket API calls for execution

That setup gives Hermes two layers to work with. The CLI handles environment and runtime management, while the API layer handles actual workflow submission and results.

ComfyUI put the interesting part plainly: the hard part was never ComfyUI's flexibility, it was finding and assembling the right pipeline. Hermes is being positioned as the layer that picks the workflow, wires the nodes, and runs it from a natural-language request.

ComfyUI's phrasing is also the best summary of the developer angle. Instead of treating Comfy as a separate app, the integration exposes its ecosystem of workflows and custom nodes as something the agent can call into programmatically.

Hermes's slash command reference says installed skills are exposed as dynamic slash commands across both main interaction surfaces. That means /comfyui is not a one-off hardcoded feature, it is how Hermes turns skills into native commands.

That detail connects this release back to Hermes's broader skill system, where the skills docs describe ~/.hermes/skills/ as the main store for bundled, hub-installed, and agent-created skills. NousResearch's earlier post hinted at the same product direction in miniature: Hermes only has to be told once.