Load workflow (current)

This is about as simple as a node gets: no inputs, one output, and its entire job is grabbing whatever workflow is currently queued and handing it out as JSON. Its only real reason to exist is feeding the "advanced" side of ComfyUI_NetDist - specifically RemoteChainStart's workflow input - so you don't have to manually export and re-import a workflow file just to send it to another instance.

NetDist is city96's pack for distributing ComfyUI execution across a second GPU or a second machine over HTTP. This particular node has nothing to do with the networking itself - it's plumbing that makes the "advanced" chain pattern (RemoteChainStart → RemoteQueueWorker → RemoteChainEnd) usable without a manual export step every time.

How it works

The schema has no required or optional inputs at all - you drop it in and connect the output, nothing to configure. It captures the workflow structure the same way ComfyUI's own queueing pathway sees it, so what comes out matches what would actually run if you queued this graph directly.

There are two natural uses: wire it straight into RemoteChainStart so every run automatically ships the live graph state to the remote workers with no stale copy to manage, or route it into SaveDiskWorkflowJSON to snapshot the current graph to disk for later reuse via LoadDiskWorkflowJSON.

The inputs and outputs that matter

No inputs. One output: "Workflow JSON" (JSON) - the current workflow, ready to feed into RemoteChainStart directly or into SaveDiskWorkflowJSON to persist it.

How to install it

Via ComfyUI Manager: search ComfyUI_NetDist. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/city96/ComfyUI_NetDist
pip install requests

Restart ComfyUI. requests is the only dependency for the entire pack - this specific node needs nothing extra.

Common issues & troubleshooting

There's genuinely not much to go wrong here - no configuration surface means nothing to misconfigure on this node specifically. A couple of things worth knowing if something looks off downstream:

The JSON doesn't match what you expected. It reflects the workflow as ComfyUI's execution pathway sees it, which is generally what you'd expect for anything actually wired up to run - but if you have disconnected or orphaned nodes sitting in your graph, don't assume they're captured the same way the visible editor state shows them.

Something's wrong further down the chain. If RemoteChainStart or a remote instance is misbehaving after wiring this in, the problem is almost certainly there, not here - this node has no logic to fail on, it's a pass-through capture.