Get Output Directory

A one-job node: it outputs the path to ComfyUI's output directory as a string. No inputs, no widgets, just an output_dir STRING on the side. It's the "keep it" counterpart to JNodes_GetTempDirectory - where temp is scratch space that vanishes on restart, output is where your finished generations actually live.

The point is portability. Instead of typing an absolute path that's different on every machine and every OS, you ask ComfyUI where its output folder is and let the answer flow into whatever needs it. If you're building a workflow that assembles custom save paths, points a loader at previously-generated images, or drives a folder-scanning node, this is how you anchor to the right place without hardcoding.

How it works

There's no real mechanism. At run time the node resolves ComfyUI's configured output directory and emits it as a string. Because it's resolved live, it's correct for the install it runs on - the whole value is that the path is right by construction rather than by you remembering to update it.

The inputs and outputs

No inputs. One output: output_dir (STRING), the absolute path to the output folder. You wire it into anything expecting a directory or base path - JNodes_SelectRandomFileFromDirectory to pull a random file back out of your generations, a save node's path field, or string-concatenation nodes that build a full filename. Its obvious sibling is JNodes_GetTempDirectory; between the two you can address either of ComfyUI's standard folders without touching a literal path.

How to install it

Via ComfyUI Manager: Install Custom Nodes, search "JNodes", install, restart. Or by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/JaredTherriault/ComfyUI-JNodes
pip install -r ComfyUI-JNodes/requirements.txt

then restart ComfyUI. No model downloads. It comes in with the rest of JNodes - Jared Therriault's grab-bag of UX and utility nodes - but this one has essentially no footprint of its own.

Common issues & troubleshooting

It's a directory, not a full file path. The output is the folder with no filename attached. If a downstream node wants a complete path to a file, concatenate a name onto it with a string node - this just gives you the base.

It reflects ComfyUI's configured output, which may be relocated. Some installs point the output directory somewhere custom via launch args. That's fine - the whole reason to use this node is that it returns that configured path rather than an assumed default. If files aren't landing where you expect, the node isn't wrong; your ComfyUI is configured to a different output folder than you thought, and this node is telling you the truth.

On hosted or serverless ComfyUI, the output folder may not persist between runs. In a managed environment the output directory can be per-execution. The path this node returns is still correct for the current run; just don't assume something written there is visible in a later, separate run. That's the environment's behavior, not the node's.

There's genuinely not much to trip over. It removes one small "works on my machine" fragility from a graph, and that's the entire job.