skills.rest
TurkeyC
TurkeyCCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

comfyui-node-migration

Migrate ComfyUI V1 custom nodes to the V3 API with Schema-based definitions.

Updated May 29, 2026
Search Tags:#python#migration#extension#guides#node#comfyui#v1-v3
One-click install
npx skills add https://github.com/TurkeyC/Dotfiles --skill comfyui-node-migration-turkeyc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comfyui-node-migration
Source: https://github.com/TurkeyC/Dotfiles/tree/main/private_dot_copilot/skills/comfyui-custom-node-skills/skills/comfyui-node-migration
Command: npx skills add https://github.com/TurkeyC/Dotfiles --skill comfyui-node-migration-turkeyc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assists developers in updating ComfyUI custom nodes from the legacy V1 API to the modern V3 API, ensuring compatibility and better maintainability.

Core Features & Use Cases

  • Guides the migration: update base classes, rename methods, update schemas, and adopt ComfyExtension-based registration.
  • Includes a side-by-side mapping between V1 and V3 concepts and practical code changes.
  • Use Case: You have a set of V1 custom nodes you want to deploy in a V3-powered environment with minimal downtime.

Quick Start

Migrate a sample V1 node to the V3 API by applying the updated class structure and using the ComfyNode-based execution flow.

Frequently Asked Questions about comfyui-node-migration

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

FAQPage Schema
How do I migrate ComfyUI custom nodes from V1 to the V3 API?▼

Migrate ComfyUI V1 nodes to V3 by rewriting classes to extend io.ComfyNode, converting inputs/outputs to Schema-based definitions, and using classmethod execute to return io.NodeOutput.

What is the difference between ComfyUI V1 and V3 node execution?▼

ComfyUI V3 node execution enforces classmethod execute, requires returning io.NodeOutput, uses fingerprint_inputs and validate_inputs, and requires no instance state compared to the V1 API.

Does ComfyUI V3 require updating custom node registration?▼

Yes, ComfyUI V3 requires adopting ComfyExtension-based registration for custom nodes, replacing the legacy V1 registration mechanism for compatibility and maintainability.

How do I handle hidden inputs when upgrading ComfyUI nodes to V3?▼

Upgrading to ComfyUI V3 involves updating hidden inputs access within the Schema-based definition, alongside base class changes and execution naming for the io.ComfyNode extension.

Can I keep instance state in my ComfyUI V3 custom nodes?▼

No, ComfyUI V3 custom nodes require no instance state; the classmethod execute must handle execution flow using fingerprint_inputs and validate_inputs.

What are the limitations when migrating legacy ComfyUI nodes to V3?▼

Migration to V3 requires strict adherence to Schema-based definitions, classmethod execute, and io.NodeOutput returns, meaning legacy instance states and V1 base classes must be completely rewritten.

Related Skills

Explore More Software Engineering Skills→
TurkeyCTurkeyC

comfyui-node-basics

Generate ComfyUI V3 custom nodes with a canonical structure template.

Community
Intermediate
jtydhr88jtydhr88
265

comfyui-node-basics

Automate V3 ComfyUI node creation and registration with io.Schema and ComfyExtension.

Community
Basic
jtydhr88jtydhr88
265

comfyui-node-outputs

Return data and UI previews from ComfyUI nodes using NodeOutput and ui helpers.

Community
Intermediate
marduk191marduk191
9

comfyui-nodes

Develop and debug ComfyUI custom nodes across V1 and V3 APIs.

Community
Advanced