Who it is forA content creator or designer with a GPU machine running ComfyUI who wants to produce visuals without building node graphs by hand.
The problemComfyUI workflows are powerful but time-consuming to set up, and results are scattered across folders.
The outcomeGenerated images or videos previewed in the control panel, with optional LLM-expanded prompts and AI upscaling.
What you need first
- Python 3.9+ and Node.js 18+ on the control machine
- A target machine with llama.cpp, vLLM, or ComfyUI already installed, or installable through the tool
- Network or SSH access to any remote target you want to manage
Steps
- Run
cd backendthenpip install -r requirements.txt, thenuvicorn app.main:app --host 127.0.0.1 --port 8000 - In a second terminal, run
cd frontendthennpm install && npm run dev, and openhttp://localhost:3000 - On Settings, add the target machine that runs ComfyUI and test the connection
- On Model Store, download an image or video model such as FLUX.1 or SDXL
- Open the image and video generation area, enter a prompt or let an LLM expand it, run the job, and preview the result
Prompt for your agent
Using the repo htobty/ReadyLLM, start the backend and frontend, connect the ComfyUI target <target-name>, and generate one text-to-image result from the prompt <prompt-text>. Report where the output file is previewed and confirm the preview loads in the control panel.
Caveat. ComfyUI on the target listens on its own loopback address by default, so finished-clip preview is proxied through the backend when the control side cannot reach it directly.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for htobty/ReadyLLM and "Generate images and short videos through ComfyUI"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer