Claude Code in ComfyUI: Build Workflows with AI Agents

If you’ve spent more time hunting for nodes and dragging connection wires than actually generating images, Comfy Pilot is worth 20 minutes of your time. It gives Claude Code full access to your ComfyUI instance through an MCP server, so you can describe what you want and let the agent build the workflow. I’ve tested it on local setups and cloud GPU instances — here’s exactly how to get it running.

🔍 What is Comfy Pilot?

Comfy Pilot is a ComfyUI custom node that does two things: it runs an MCP (Model Context Protocol) server that gives Claude Code direct access to your workflow, and it embeds a full xterm.js terminal right inside the ComfyUI browser tab. The MCP server is the important part — it exposes a set of tools that let Claude see your current graph, create and connect nodes, run the workflow, view generated images, and download models from Hugging Face or CivitAI.

The embedded terminal solves a specific pain point: cloud GPU services like RunComfy don’t give you shell access, so you couldn’t use Claude Code with them before. Comfy Pilot changes that. You open the terminal tab inside ComfyUI and run Claude Code directly from there, no SSH required.

It was built by Constantine (ConstantineB6 on GitHub), is available in the ComfyUI Registry, and is actively maintained — the latest version is v1.0.24 as of March 2026.

⚡ Why Use Claude Code with ComfyUI?

The straightforward answer: building complex workflows is tedious by hand. Comfy Pilot lets you describe what you want and have it built, connected, and running — without touching a single drag handle.

✅ Natural language workflow building — “Build me a FLUX schnell workflow with a ControlNet preprocessor” creates the full node graph, connections included.
✅ Real-time image feedback — Claude can view outputs from Preview Image and Save Image nodes and suggest workflow adjustments based on what it sees.
✅ Model downloads without leaving ComfyUI — Download from Hugging Face, CivitAI, or direct URLs through a single command.
✅ Custom node management — Search, install, uninstall, and update nodes from the ComfyUI Manager registry without touching the UI.
✅ Works on cloud GPU instances — The embedded terminal bridges the gap for services with no shell access.
✅ Extensible via Claude Code skills — Add domain-specific workflow knowledge through CLAUDE.md or the skills index at skills.sh.

🖥️ System Requirements

Worth noting: the Max Plan gives you unlimited Claude Code usage, which matters here — building a complex workflow can burn through 10–20 agentic tool calls per session. Free tier users will hit rate limits quickly.

✅ Step 1 – Install Comfy Pilot

You have three options. The CLI method is fastest if you already have the comfy CLI installed:

comfy node install comfy-pilot

If you prefer ComfyUI Manager:

1. Open ComfyUI and click Manager
2. Click Install Custom Nodes
3. Search for Comfy Pilot
4. Click Install
5. Restart ComfyUI

Or clone it directly into your custom nodes folder:

cd ~/Documents/ComfyUI/custom_nodes
git clone https://github.com/ConstantineB6/comfy-pilot.git

After installation, restart ComfyUI. You’ll see a floating Claude Code terminal panel in the top-right corner of the interface. The MCP server starts automatically when ComfyUI loads.

✅ Step 2 – Install Claude Code CLI

Comfy Pilot will install the Claude Code CLI automatically if it can’t find it on your system. If you want to install it manually first:

macOS / Linux / WSL:

curl -fsSL https://claude.ai/install.sh | bash

Windows (PowerShell):

irm https://claude.ai/install.ps1 | iex

Windows (CMD):

curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

After installing, authenticate with your Anthropic account:

claude login

This opens a browser tab to link your account. You’ll need either a Claude.ai subscription or an ANTHROPIC_API_KEY environment variable for API billing.

💡 Tip: The Claude Code Max Plan ($100/month) is worth it if you plan to use Comfy Pilot regularly. The free tier is fine for experimenting, but building and iterating on a multi-step workflow can easily hit the daily message cap within a single session.

✅ Step 3 – Configure the MCP Server

Comfy Pilot auto-configures the MCP server on startup by writing to ~/.claude.json. In most cases you don’t need to do anything — restart ComfyUI and the tools are registered.

If something goes wrong and Claude can’t see the ComfyUI tools, add the server manually to ~/.claude.json:

1
{
2
  "mcpServers": {
3
    "comfyui": {
4
      "command": "python3",
5
      "args": ["/path/to/ComfyUI/custom_nodes/comfy-pilot/mcp_server.py"]
6
    }
7
  }
8
}

Replace /path/to/ComfyUI with your actual ComfyUI directory. On Windows, use python instead of python3.

To verify the connection is working, open the Comfy Pilot terminal and run:

claude --mcp-debug

You should see comfyui listed as a connected MCP server with all 13 tools available: get_workflow, summarize_workflow, edit_graph, view_image, run, download_model, and the custom node management tools.

✅ Step 4 – Build Your First Workflow

With the MCP server connected, open the Comfy Pilot terminal inside ComfyUI and start Claude Code:

claude

From here, describe what you want in plain language. Here are a few prompts that work well out of the box:

Build a workflow from scratch:

1
Build me a FLUX.1 schnell workflow with a basic KSampler.
2
Include positive and negative prompt inputs.

Inspect what’s already there:

1
What nodes are in my current workflow? Give me a summary of what it does.

Modify an existing setup:

1
Add a ControlNet preprocessor between the image input and the KSampler.
2
Connect it correctly and position the new nodes to the left of the sampler.

Run the workflow and review output:

1
Run the workflow and show me what was generated.

Claude uses the edit_graph tool to create, connect, position, and configure nodes in batch operations. Before making any changes, it calls summarize_workflow to read the current state — which prevents misconnections. The view_image tool then lets it analyze the output and suggest next edits.

In practice, building a standard FLUX workflow from scratch takes Claude roughly 8–15 tool calls. The whole process runs inside the browser tab if you’re on a cloud instance.

✅ Step 5 – Download Models and Manage Custom Nodes

Comfy Pilot handles model downloads and node management — the two tasks that usually mean leaving ComfyUI entirely.

Download a model:

1
Download the FLUX.1 dev model from Hugging Face to my checkpoints folder.

Supported sources: Hugging Face (including gated models with HF token auth), CivitAI, and direct download URLs. The download_model tool routes files to the correct ComfyUI/models/ subdirectory automatically.

Find and install a custom node:

1
Search for a ControlNet node that works with FLUX and install it.

Claude uses search_custom_nodes against the ComfyUI Manager registry, selects the best match, and calls install_custom_node. You get a summary of what was installed and any restart instructions.

Check for node updates:

1
Are any of my installed custom nodes outdated? Update them.

💡 Tip: After installing new custom nodes through Claude, restart ComfyUI before asking it to use them. New node types won’t show up in get_node_types until the ComfyUI server has rescanned the custom nodes directory.

🛠️ Troubleshooting

💡 Tips & Best Practices

💡 Tip: Add a CLAUDE.md file to your ComfyUI folder describing your preferred defaults — sampler, scheduler, step count, which custom nodes you have installed. Claude reads it on startup and skips the back-and-forth of figuring out your setup from scratch every session.

💡 Tip: Always ask Claude to summarize your workflow before modifying it. If it operates on a stale graph state, connections go in wrong places. The summarize_workflow call takes one tool turn and prevents several broken ones.

💡 Tip: For cloud GPU services without terminal access (like RunComfy), use the Comfy Pilot embedded terminal exclusively. For RunPod and Vast.ai where SSH is available, you can run Claude Code from either your local terminal or the embedded one — both connect through the same MCP server.

💡 Tip: Restrict what Claude is allowed to do for production workflows. Add explicit instructions to CLAUDE.md like “Do not download models or install nodes without checking with me first.” Open-ended agent permissions are useful for building but risky when you’re running a stable workflow you don’t want changed.

💡 Tip: The skills.sh skill index has ComfyUI-specific skills covering node types, sampler behavior, and common workflow patterns. Installing a relevant skill before a session means Claude needs fewer clarification turns to understand what you’re working with.

💡 Tip: If you’re hitting the Claude free tier limit mid-workflow, save your current graph as a JSON file before the session ends. When you start a new session, tell Claude to load the saved workflow file and continue from where you left off — edit_graph can apply changes to any graph state, not just what’s currently in the browser.

✅ Final Thoughts

Comfy Pilot genuinely changes how you interact with ComfyUI. For simple workflows you’ve built dozens of times, it won’t save you much. But for anything complex — multi-model pipelines, unfamiliar ControlNet setups, or experimenting with node combinations you’ve never tried — being able to describe what you want and have it built is faster than the alternative.

The security concerns from the community are worth taking seriously. The WebSocket endpoints are localhost-bound by default, but the auto-download behavior and lack of confirmation prompts for destructive operations are real limitations. Run Comfy Pilot on trusted machines or in a sandboxed environment, and use CLAUDE.md restrictions to keep Claude from making changes you didn’t ask for.

✅ Compatible with ComfyUI Desktop and portable installs
✅ Cloud GPU ready via embedded terminal
✅ Actively maintained — v1.0.24, March 2026
✅ Extensible with Claude Code skills

Happy generating!

❓ FAQ

❓ Q: Does Comfy Pilot work with ComfyUI Desktop or only the web browser version?

A: Comfy Pilot works with both. Since it runs as a server-side custom node, the MCP server and embedded terminal are available regardless of whether you access ComfyUI through a browser or the Desktop app.

❓ Q: Do I need a paid Claude subscription to use Comfy Pilot with ComfyUI?

A: No, but the free tier hits rate limits quickly when Claude is making 15–20 tool calls per workflow build. The Max Plan ($100/month) removes usage caps and is the practical choice for regular use. Alternatively, using the ANTHROPIC_API_KEY environment variable gives you pay-per-token billing through the API.

❓ Q: Can Comfy Pilot use a local LLM like Ollama instead of Claude?

A: Not natively — the MCP server is built for Claude Code’s tool format specifically. The claude-code-comfyui-nodes project by christian-byrne offers more flexibility in how the Claude Code SDK is configured, and there’s community interest in local LLM support, but nothing officially released as of March 2026.

❓ Q: Does Comfy Pilot work on RunPod or Vast.ai cloud GPU instances?

A: Yes. RunPod and Vast.ai both give SSH terminal access, and Comfy Pilot’s MCP server runs alongside the ComfyUI process. The embedded terminal is specifically useful for cloud platforms like RunComfy that don’t provide shell access. Multiple users in the r/comfyui thread confirmed it works on RunPod without setup issues.

❓ Q: Can Claude Code handle subgraphs inside ComfyUI workflows?

A: Not as of March 2026 — Comfy Pilot’s edit_graph tool operates on the top-level graph only. If your workflow uses subgraphs extensively, Claude won’t be able to inspect or modify them. This was flagged by users in the original Reddit thread as a known limitation.

❓ Q: Is there a security risk to running Comfy Pilot locally?

A: The WebSocket endpoints are bound to localhost, so nothing is exposed to the internet in a typical setup. The main risks are auto-model-downloads from arbitrary URLs and Claude making workflow changes without confirmation. Mitigate both by adding clear restrictions to your CLAUDE.md and running Comfy Pilot inside a VM or sandboxed environment if you’re cautious.

📚 Additional Resources

• Comfy Pilot GitHub — ConstantineB6
• Claude Code ComfyUI Nodes — christian-byrne
• Claude Code CLI — claude.ai/code
• Claude Code Skills Index — skills.sh

📚 Related Guides

• Install FLUX in ComfyUI: Complete Setup Guide
• ComfyUI Portable vs Desktop
• Best AI Coding Assistants: Cursor vs Copilot vs Claude
• FP8 vs BF16 in ComfyUI
• Run ComfyUI in the Cloud: Comfy Cloud vs Alternatives
• OpenCode Setup Guide: The Ultimate Open Source AI Agent