ComfyUI Base Path

ComfyUI Base Path is the definition of a plumbing node: no inputs, one output, and its only job is to hand you a STRING containing your ComfyUI installation directory. That's it. base_path comes out as the folder where ComfyUI's folder_paths module lives, with backslashes normalized to forward slashes so it behaves the same on Windows and everything else.

Why would you want that on the canvas? Because this pack is path-hungry. Several of its nodes - SimpleImageLoader, FilePathProcessor, VideoMerger, EDLSceneParser, even MovingTitles' srt_path - take absolute paths as strings rather than the nicer drag-and-drop file pickers ComfyUI core gives you. If you're assembling those paths from other nodes, you need a single source of truth for "the root of the install," and this is exactly the one-source-many-consumers pattern the KB's node-plumbing essay describes: define the base once, fan it out, never hardcode a path in a widget again.

What you get

• base_path (STRING) - e.g. C:/ComfyUI or /home/you/ComfyUI, forward-slashed.

That's the whole node. You wire it into a string-concatenation node to build base_path + "/models/checkpoints/...", or feed it into whichever pack node wants a directory.

Install

Same pack install as everything else from lazniak's videoclipgenerator:

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

Or just search "videoclipgenerator" in ComfyUI Manager and click install. Restart, and the node appears under the "utils" category. It imports folder_paths from the running ComfyUI, so it can't really go wrong at runtime - no dependencies, no models, no network.

Gotchas and honest take

The main thing to know is what it does not do: it returns the ComfyUI install root, not ComfyUI's output or input folder - if that's what you want you'll still be concatenating /output onto it yourself. And while the README for the pack promises fancy extras like environment detection and path sanitization, the actual code is a ten-line function: resolve the folder_paths module's directory, forward-slash it, return. That's the pack in a nutshell, honestly - ambitious README, simple code. The simple code is fine here. It's a boring, correct utility node, and for a utility node that's the highest compliment.