Nodes/radiance/◎ Radiance Workspace
ComfyUI Node

◎ Radiance Workspace

The node that treats your whole workflow as a saveable project

By fxtdstudios·Created 7 months ago·Updated 9 days ago· 242
◎ Radiance Workspace

      Normally a ComfyUI workflow is a graph you save as a JSON file and hope you remember where you put it. ◎ Radiance Workspace treats it like a project instead: it's a hub node you drop on the canvas that saves and loads the entire workflow as a .rad file, with versioning and a little security, so "which version of this grade did I deliver?" has an answer other than your file manager.

      The honest framing first: this node has no inputs and no outputs. It never executes. Its entire job is to exist on the canvas and expose buttons in the UI that serialize your graph - which is why the brief's info_schema is empty and why the README calls it "the command center" of a Radiance production. The heavy lifting lives in the companion JavaScript, not the Python class.

      How it works

      Under the hood, RadianceWorkspace is a no-op (FUNCTION = "noop" returns an empty tuple). The real machinery is js/radiance_workspace.js, which serializes the entire ComfyUI app graph into a secure .rad container. The .rad format is this pack's own workflow container - the README calls it a "secure .rad v2 container," and the code ships with versioning (up to 10 auto-versioned backups), a 50 MB size guard, filename length limits, and whitelisted .rad extensions.

      The workspace also plays host to the docs buttons - links out to radiance.fxtd.org and fxtd.org - and in current versions it's the anchor for project/shot/version management that the other Radiance nodes read state from. The source's docstring is blunt about the division of labor: "The actual file generation and graph rebuilding is handled natively by the companion JavaScript extension."

      What you actually do with it

      • Add it: right-click → Radiance > Project > Radiance Workspace (or it's under FXTD Studios/Radiance/Layout).
      • Set a project path if your production folder matters to you (the README's getting-started walks you through this).
      • Use its buttons to save the current graph as a .rad file, or load one back - it rebuilds the graph from the file.

      For a beginner this is a "save my work properly" upgrade over raw JSON dumps. For someone running multi-shot projects it becomes the versioning spine - old .rad workflows can be loaded through the Workspace tools when stale JSON layouts from earlier versions break (the README explicitly warns that very old workflow JSONs "may contain stale widget order or renamed nodes and should be rebuilt or imported through the current Radiance Workspace tools").

      How to install it

      Same pack, same steps. ComfyUI Manager → search "Radiance", or:

      cd ComfyUI/custom_nodes
      git clone https://github.com/fxtdstudios/radiance.git
      cd radiance
      pip install -r requirements_windows.txt
      

      Restart ComfyUI. Because the node is JS-driven, a hard refresh of the browser tab (or restarting the server) matters more here than for pure-Python nodes - if the buttons don't appear, you're almost certainly running a stale frontend bundle.

      Common issues

      The most common stumble is expecting it to do something during execution. It doesn't - it's a canvas tool, and it'll look "unused" in your prompt history, which is fine. Second: the .rad format is Radiance-specific, so don't expect other tools to read it; if you're handing a workflow to someone without Radiance, export the plain JSON instead. And because it's tied to the frontend, a ComfyUI update that changes graph serialization can break older .rad files - keep the pack updated and keep the versioned backups it makes.

      It's one of those nodes that looks like nothing until you've lost a workflow file once. After that, "save to workspace" becomes muscle memory.

      CategoryFXTD Studios/Radiance/Layout

      Inputs (0)

      No inputs

      Outputs (0)

      No outputs