Nodes/Boyonodes/Boyo Asset Grabber (Advanced)
ComfyUI Node

Boyo Asset Grabber (Advanced)

The same auto-installer, with the training wheels off — explicit paths, same caveats

By DragonDiffusionbyBoyo·Created 2 years ago·Updated 27 days ago· 16
Boyo Asset Grabber (Advanced)
    • status
    json_file
    custom_nodes_pathC:\Users\YourName\Documents\ComfyUI
    models_pathC:\Users\YourName\Documents\ComfyUI
    download_triggerfalse

    Boyo Asset Grabber (Advanced) is the Simple version with a knobs-on variant: it reads the same JSON manifest format, does the same git-clone / model-download / pip-install routine, but instead of auto-detecting your ComfyUI layout it asks you to type in the paths. It's the "my install is weird" edition. Portable installs, network drives, machines where ComfyUI isn't where the pack expects it to be - this is the one for those cases.

    How it differs from Simple

    The only real difference is two extra required inputs, both strings:

    • custom_nodes_path - where custom node folders live. Default is the author's example C:\Users\YourName\Documents\ComfyUI, which is a placeholder, not a real path - you must set this to your actual ComfyUI root or the clones will land in the wrong place.
    • models_path - where model folders live, same story.

    If your ComfyUI is in a standard location and the Simple node's auto-detection works, there is no advantage to using this one - the extra inputs are just more ways to get a path wrong. The Advanced name is about control, not capability.

    Everything else matches Simple: json_file dropdown from custom_nodes/Boyonodes/assetJsons/, download_trigger boolean (off by default), and a status STRING output that reports what happened. Manifests declare custom nodes (git URLs), model downloads, and pip packages, and the node processes all three with environment detection and per-item results.

    The two gotchas that matter

    1. The placeholder default is a trap. Leave custom_nodes_path at C:\Users\YourName\... and it will cheerfully clone custom nodes into a directory that doesn't exist - or worse, create it. Set both paths to your real ComfyUI root before first use.
    2. Same arbitrary-code warning as Simple, doubled. This node runs git clones, pip installs, and file downloads from a JSON manifest. On top of that, it lets you redirect those operations anywhere you can type. That is powerful and it is exactly what a malicious workflow would abuse. Only feed it manifests you've read and understand, and only point it at paths you control. The ecosystem's security history - the ComfyUI_LLMVISION malware incident, the general absence of sandboxing in custom nodes - is the reason this advice exists. It's a legitimate tool for sharing workflows with dependencies; it's also a foot-gun with a safety removed.

    Installation

    cd ComfyUI/custom_nodes && git clone https://github.com/DragonDiffusionbyBoyo/Boyonodes
    pip install gitpython requests
    

    restart, and find it under Boyo/Asset Management.

    Should you use it?

    Only if the Simple node genuinely can't find your install - non-standard layout, portable drive, or a remote-mounted setup. In every other case, use Simple and delete the mental overhead. And whatever you use, remember the manifest is a script wearing a JSON costume. Read it once, then enjoy the convenience.

    CategoryBoyo/Asset Management

    Inputs (4)

    NameTypeDefaultDescription
    json_fileCOMBO1 options: No JSON files found - add files to custom_nodes/Boyonodes/assetJsons/
    custom_nodes_pathSTRINGC:\Users\YourName\Documents\ComfyUI
    models_pathSTRINGC:\Users\YourName\Documents\ComfyUI
    download_triggerBOOLEANfalse

    Outputs (1)

    NameTypeDescription
    statusSTRING