PathOutput

Here's the thing about ComfyUI-ToolBox: three of its five nodes are anchored to /root and only really work on AutoDL cloud instances. PathOutput is the exception - it's the one node in this pack you can install on a home PC and actually get value from. It builds absolute paths from a dropdown and a few keystrokes, so you stop hand-typing long paths into Save nodes and text boxes.

Why bother? Because path typos are a classic ComfyUI failure mode. You type models/checkpoints and the actual folder is models/checkpoints_v2, and suddenly your load is hitting a different model than you think, or a Save writes somewhere you'll never find it. A path builder removes the guessing.

How it works

Pick a base directory from a dropdown, type relative subpaths (one per line, multiline), and the node joins them together and returns the resulting absolute paths as a single STRING, newline-separated. That's the whole mechanism - it's os.path.join with a curated list of base options instead of raw string concatenation.

The base options are where the versatility lives:

• ComfyUI - the root of your ComfyUI install
• models, checkpoints, loras, vae - the standard model folders inside ComfyUI (checkpoints/loras/vae resolve to ComfyUI/models/<name>)
• custom_nodes, input, output - the other familiar ComfyUI directories
• BasicPath - whatever basic_path is set to in the pack's config.yaml (default /root, so it's the AutoDL-friendly option)
• UserHome - your home directory, wherever that is
• site-packages - the current Python environment's package install location

Notice that only BasicPath is cloud-specific. Everything else resolves against your actual ComfyUI install, home directory, or Python environment - which is why this node travels well.

The inputs that matter

• base_dir - the dropdown above. This is the one to get right.
• subpaths - one relative path per line. loras/my-characters under the loras base gives you the full path to that folder.

Its single output, paths, is the built absolute paths - newline-joined if you gave it more than one subpath.

The combo that's actually good

Wire PathOutput into the pack's CreatePaths node (output_paths → input_paths), and you've got a workflow that builds every path you need and guarantees the folders exist before any Save node runs. Paths built correctly, then made real. That's the killer pairing in this pack, and neither half cares whether you're on AutoDL or a local rig.

Installing it

Same as every node in the pack:

# via ComfyUI Manager: search "ComfyUI-ToolBox", install, restart
cd ComfyUI/custom_nodes
git clone https://github.com/hben35096/ComfyUI-ToolBox

No model files, no heavy dependencies - just the pack's single codewithgpu requirement, which Manager installs automatically (or pip install -r requirements.txt after a manual clone).

Where people trip up

• BasicPath is whatever config.yaml says. It's not a magic "my models folder" - it's /root by default. If you're not on AutoDL, use ComfyUI, input, output, or UserHome instead, or you'll get paths that don't exist.
• No existence check. PathOutput builds strings; it doesn't verify the folders are there. That's literally what CreatePaths is for - use them together.
• Multiline behavior. Blank lines are stripped, so don't sweat stray newlines. But note it's one subpath per line - jamming two on one line will not do what you want.

Is it the most exciting node on the graph? No. But it's the difference between typing /home/you/ComfyUI/models/loras/ from memory and having it handed to you correctly every time. For a pack aimed at cloud workflows, it's the piece with the longest shelf life.