comfyui

Launch Hermes agent and WebUI on Windows with a shared Python environment.

31|3|Updated May 7, 2026
One-click install
npx skills add https://github.com/markwang2658/hermes-windows-native --skill comfyui-markwang2658
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comfyui
Source: https://github.com/markwang2658/hermes-windows-native/tree/main/hermes-agent/skills/creative/comfyui
Command: npx skills add https://github.com/markwang2658/hermes-windows-native --skill comfyui-markwang2658

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, websocket-client, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Hermes Windows Native provides a Windows-native integration that runs Hermes Agent and Hermes WebUI with a shared Python environment.

Core Features & Use Cases

  • Fixed Windows-native directory layout with a single shared .venv for both components.
  • One-click startup via PowerShell launcher to bring up the agent and UI with logs split across windows.
  • CLI-driven lifecycle and REST/WS API access for automation, provisioning, and workflows.

Quick Start

Use the Windows-native comfyui skill to install and launch Hermes on Windows in one step.

Frequently Asked Questions about comfyui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a shared Python environment for Hermes Agent and WebUI on Windows?

Use the Windows-native ComfyUI skill to configure a fixed directory layout with a single shared .venv, enabling both Hermes Agent and Hermes WebUI to run within one unified Python environment.

Can I automate Hermes startup with a one-click launcher on Windows?

Yes, you can automate Hermes startup using a PowerShell launcher that brings up the agent and UI simultaneously, splitting runtime logs across separate windows for easy monitoring.

Does comfy-cli support lifecycle management for Hermes workflows?

comfy-cli provides CLI-driven lifecycle management for Hermes, supporting automated provisioning, REST/WS API access, and workflow routing for Windows-native deployments.

What is the required repository structure for Windows-native Hermes integration?

The integration enforces a fixed repository layout containing scripts/, references/, and a shared .venv directory to support installation, launch, and runtime routing.

Why does my Hermes setup require separate virtual environments for the agent and UI?

It does not; the Windows-native integration specifically uses a single shared .venv for both Hermes components to avoid dependency conflicts and simplify environment management.