Nodes/ComfyUI-Studio-Fury/1️⃣ SF Project Manager (Start)
ComfyUI Node

1️⃣ SF Project Manager (Start)

The bus starts here — SF Project Manager is the node that defines your whole StudioFury project

By FuryNocturn·Created 9 months ago·Updated 4 months ago· 0
1️⃣ SF Project Manager (Start)
  • clip
  • vae
  • bus
project_nameMy_Epic_Movie

Every StudioFury workflow starts here, and I mean that structurally, not just cosmetically. SF Project Manager is the "1️⃣" in a pack whose nodes are literally numbered 1 → 2 → 3. It takes your checkpoint's CLIP and VAE plus a project name, and it produces the thing every other node in this pack consumes: the SF_LINK bus.

So what is a bus? It's a plain Python dict that gets threaded through the whole graph - one wire carrying project name, your CLIP, your VAE, and later every entity you register. Think of it as the pack's answer to "spaghetti wiring." Instead of running a CLIP wire and a VAE wire all over the place, you set them once here and they ride along inside the bus. ComfyUI treats SF_LINK as an opaque custom type, so you'll get a distinct colored cable, and you can only connect it to other StudioFury nodes.

The clever bit is that it creates your project folder on disk as soon as you run it: ComfyUI/output/StudioFury/<project_name>/ with Characters, Scenes, Renders, and Cache subfolders. Everything the Director Engine and Smart Saver write later lands there, keyed by the same project name. Get the name right once and the whole pipeline stays consistent - that's the entire point of the pack.

The inputs that matter:

  • clip and vae - straight from your checkpoint loader (or a separate VAE loader). These get cached inside the bus so no later node needs them wired directly.
  • project_name - a string. This is your identity across saves and loads, so make it meaningful (My_Epic_Movie is the default, but you'll thank yourself for something less generic).

The output: one bus (SF_LINK). Wire it into SF Add Entity next. That's the whole job - this node is a starting gate, not a workhorse.

Install

In ComfyUI Manager, search for ComfyUI-Studio-Fury and hit Install, then restart. Or, from a terminal:

cd ComfyUI/custom_nodes/
git clone https://github.com/FuryNocturn/ComfyUI-Studio-Fury

Then restart ComfyUI. Good news: requirements.txt only lists torch, Pillow, numpy, and aiohttp - all of which ComfyUI already ships. No model downloads, no heavy install, no missing weights to hunt down.

Gotchas

A few honest notes. This is a small, single-author pack (StudioFury by FuryNocturnTV, MIT licensed) with essentially no community footprint yet - zero reddit discussion, barely any comfy.icu impressions as of this writing. That means the docs are the docs, and you're the beta tester. If a node misbehaves, check the console log - the pack is chatty in a good way and prints what it's doing to stdout.

One real quirk: the bus only lives as long as your workflow run. It's a runtime dict, not persisted - the Project Manager creates the folder structure, but your entities and renders are saved to disk by the Director Engine or Smart Saver, not by the bus itself. And if you change the project name mid-graph, you've effectively started a new project folder. Decide the name once, wire the CLIP and VAE in, and let the bus do the rest. The pack calls this node "The root node" and that's exactly how to treat it: it's the first thing you place and the thing everything else hangs off.

Category🧩 Studio Fury/📦 Dataset

Inputs (3)

NameTypeDefaultDescription
clipCLIP
vaeVAE
project_nameSTRINGMy_Epic_Movie

Outputs (1)

NameTypeDescription
busSF_LINK