comfyui
Install and operate the MAGI-1 ComfyUI custom node and bundled workflows.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- comfyui
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Install and operate the MAGI-1 ComfyUI custom node and bundled workflows.
- disable-model-invocation
- true
02 资源文件 6
- 参考文档references/comfyui-nodes-and-workflows.md10.9 KB
- 参考文档references/troubleshooting.md8.4 KB
- 参考文档references/workflows/magi_image_to_video_example.json4.7 KB
- 参考文档references/workflows/magi_text_to_video_example.json4.0 KB
- 参考文档references/workflows/magi_video_continuation_example.json4.8 KB
- 脚本scripts/inspect_workflow_nodes.py6.9 KB
03 SKILL.md 正文
MAGI-1 ComfyUI operating skill
Use this sub-skill when a user wants to install, recognize, run, adapt, or troubleshoot the MAGI-1 ComfyUI custom node and its example workflows.
Do not use this sub-skill for source-code CLI inference commands or direct MagiPipeline API usage; route those questions to the MAGI-1 inference sub-skill. ComfyUI itself is an external host application dependency; this skill captures MAGI node behavior and workflow adaptation, not a verified ComfyUI host import.
Fast operating path
- Install ComfyUI, then install the MAGI-1 node by one of these choices:
- Registry install from inside the ComfyUI directory:
comfy node registry-install MAGI-1. - Source install by placing the MAGI-1 source tree under
ComfyUI/custom_nodes/MAGI-1and installing MAGI-1 runtime dependencies into the same Python environment used by ComfyUI.
- Registry install from inside the ComfyUI directory:
- After either install method, ensure ComfyUI sees a plugin-root
__init__.py: move or copy the repository'scomfyui/__init__.pyto the MAGI-1 plugin root if it is not already there. The plugin root must still contain thecomfyui/,inference/, andexample/assets/subtrees expected by that initializer. - Download model weights and edit the selected MAGI JSON config so checkpoint paths are absolute for
load,t5_pretrained, andvae_pretrained. Use absolute paths for the ComfyUI node'sconfig_path, T5 path, input media, and save path fields. - Launch ComfyUI with
comfy launchorpython main.pyfrom the ComfyUI directory. - Add nodes from Add Node → Magi or import one of the bundled workflows, then replace every placeholder path before queueing the graph:
Detailed references
- Node roles, inputs, outputs, task-mode behavior, installation notes, and workflow adaptation: references/comfyui-nodes-and-workflows.md
- Troubleshooting path, import failures, absolute-path errors, GPU/memory issues, and output-saving issues: references/troubleshooting.md
- Offline workflow inspection helper: scripts/inspect_workflow_nodes.py
Guardrails for future agents
- State that imported workflow JSONs contain placeholders and must be reassigned inside the user's ComfyUI runtime.
- State that MAGI's ComfyUI
MagiProcessnode sets single-node/single-GPU distributed environment variables internally before inference. - Do not claim ComfyUI host imports were verified unless the user has actually run ComfyUI with the MAGI node in their environment.
- Keep all workflow links generated-skill-relative; do not link to source checkout files.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).