🦊 Kumiho Create Edge

Let's get the honest part out of the way first, because it will save you twenty minutes: Kumiho Create Edge, in the current release, does not actually create an edge. Read the shipped source and you'll find the method body is a TODO: Implement actual Kumiho API integration that returns a deterministic ID computed from your inputs. It reports success the way a parking meter reports change - locally, convincingly, with nothing real behind it.

The design intent is clear enough. Kumiho's whole pitch is a dependency graph over your assets - "what breaks if I change this model?" - and edges are the glue. The node is meant to draw a relationship between two revisions by hand: source_kref is the asset that depends, target_kref is what it depends on, and edge_type names the relationship. You get eight choices, and they split into two families: the SDK-native ones (DEPENDS_ON, DERIVED_FROM, REFERENCED, CONTAINS, CREATED_FROM) and the lineage-style ones the save path uses (USED_MODEL, USED_LORA, USED_INPUT). There's also an optional metadata_json for attaching notes to the edge, and a single edge_id string comes back out - which, today, is an md5 hash of source+target+type. Deterministic, stable, but it exists only in your session.

So what do you actually use it for right now? Not much, honestly - unless you're building the graph where this node will slot in later and want to keep the wiring honest. Don't build a workflow that depends on edges showing up in Kumiho Cloud, because they won't.

Here's the thing the README buries: real edges already get created for you. Kumiho Save Image and Kumiho Save Video parse your workflow, detect the checkpoints, LoRAs, VAEs and input images, and call the SDK's revision.create_edge() with DEPENDS_ON / REFERENCED and friends - actual cloud-side edges. The lineage you want from Create Edge is already being written by the save nodes, automatically. This node is the manual-edit affordance that's still under construction.

Install & troubleshooting

It ships with the kumiho-comfyui pack: ComfyUI Manager → search "Kumiho", or git clone https://github.com/kumihoclouds/kumiho-comfyui into custom_nodes plus pip install -r requirements.txt, then authenticate once with pip install kumiho-cli and kumiho-cli login.

Troubleshooting is short because there's nothing to break: any non-empty inputs give you an edge_id, always. The failure mode is expectations, not errors. If you need to check whether edges exist yet, skip this node and read the lineage_json output of a Kumiho Save node - that's where the real relationship data lives today. And if you're relying on this pack for impact analysis, keep an eye on releases; this is the node that lights up when the backend ships.