FolderViewe

The node is called FolderViewe - spelled exactly like that, "Viewe", missing the second 'e' - and no, you didn't mistype it in the search box. That's the class name the author registered, and it's the kind of small quirk you just learn to live with in the custom-node ecosystem. It's a directory lister: give it a path, get back the contents as text, right there in the graph.

If that sounds underwhelming, it's because it is - in the best way. It's a debug tool. It exists so you can check what's actually in a folder without SSHing into your box or digging through a file browser, which matters more than it sounds like when you're working on a rented AutoDL instance.

How it works

The mechanism is a one-liner with a couple of branches. It joins your target_path onto /root (the pack's hardcoded base - AutoDL's home directory), calls os.listdir() on it, and joins the results with newlines into a single STRING output. Two decisions in the code are worth knowing:

• Dotfiles are hidden by default. Anything starting with . is filtered out unless you flip the toggle.
• Bad paths don't crash the run. If /root/<target_path> doesn't exist, you get a status string back saying it's not a valid path - in Chinese - instead of an exception killing your workflow.

So the output is either a file list (one per line) or a "that path isn't real, check it" message. It's meant to be read by you, not fed into a pipeline.

The inputs that matter

Only two, and both are self-explanatory:

• target_path - the folder to list, relative to /root. models/checkpoints lists your checkpoints; output lists your renders.
• include_hidden - flip it on if you want to see dotfiles and dot-directories too.

The safe pairing

FolderViewe is the natural partner to the pack's FolderDeleter: look at what's in a directory first, confirm you're targeting the right one, then delete. On an AutoDL box where storage is metered and every session starts from a fresh-ish state, "list before you delete" is the difference between cleaning up a stray checkpoint and nuking the folder you meant to keep. It's also handy for confirming a model actually landed where AutoDLDownload said it would.

Installing it

Identical to the rest of the pack:

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

It lives in commonly_node.py with AutoDLDownload and FolderDeleter. No model files, no extra dependencies beyond the pack's single codewithgpu requirement (Manager handles it; pip install -r requirements.txt if you cloned manually).

Where people trip up

• The /root anchoring. Same as the pack's other common nodes, paths are always relative to /root. On a local machine that's probably not where your files are, so the node will keep telling you paths are invalid - it's not broken, it's pointed at the wrong base.
• Chinese status messages. "不是有效的路径" means "not a valid path." Success is just the list of filenames, which needs no translation.
• The whole node vanishing. If FolderViewe isn't in your node list after install, the shared commonly_node.py module failed to load - check that codewithgpu is installed, because that import sits at the top of the file and takes all three nodes down with it.

It's a humble utility, and it won't be the reason you install this pack. But the day you need to confirm what's sitting in /root/models/checkpoints at 2am on a rented GPU, you'll be glad it's there.