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

Boyo Asset Grabber (Simple)

A workflow that installs its own nodes, models, and pip packages — handy and a little scary

By DragonDiffusionbyBoyo·Created 2 years ago·Updated 27 days ago· 16
Boyo Asset Grabber (Simple)
    • status
    json_file
    download_triggerfalse

    Imagine downloading a workflow and instead of a wall of "missing nodes" errors, the workflow downloads everything it needs to run. That's the idea behind Boyo Asset Grabber (Simple): you give it a JSON manifest, flip a switch, and it git-clones custom nodes, downloads models, and pip-installs Python packages automatically. It's the author's answer to the single most complained-about part of ComfyUI - the dependency treadmill where you spend more time installing missing pieces than generating.

    Now the part that should make you pause: this node runs arbitrary commands. It clones from git URLs, installs pip packages into your environment, and downloads files, all from a JSON file that a workflow author controls. That's a lot of power sitting behind a boolean toggle, and it's the exact class of capability the ecosystem's security incidents have been built on. It's fine if you wrote the manifest yourself or you trust the source completely. It's a terrible idea to flip download_trigger on a manifest you grabbed from a stranger's workflow without reading it.

    How it works

    The node scans custom_nodes/Boyonodes/assetJsons/ and lists the JSON files there in a dropdown. The Simple version auto-detects your ComfyUI layout - it derives the ComfyUI root from the pack's own location and finds your Python environment's pip - so there's nothing to configure. The Advanced sibling is identical but adds explicit custom_nodes_path and models_path overrides for non-standard installs.

    You pick a manifest, set download_trigger to true, and it processes the JSON, which declares:

    • custom_nodes - git repos to clone into custom_nodes/,
    • models - files to download into model folders,
    • pip packages to install.

    The status (STRING) output streams back a report of what succeeded, failed, or was skipped - that's how you know whether your env got nuked or just augmented.

    The two inputs that matter

    • json_file - the manifest dropdown. If you see "[No JSON files found - add files to custom_nodes/Boyonodes/assetJsons/]", that's your cue: drop a manifest there.
    • download_trigger - false by default, which is good. It's labelled like a button ("Download Assets" when off, "Ready" when on) and the node even refuses to re-run while a download is in progress.

    Installation

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

    restart. (gitpython and requests are the two packages the node itself needs - the README's full requirements list covers the whole pack, but this node works with just those.)

    The honest warning

    I'll say it plainly because the ecosystem history demands it: custom nodes execute arbitrary Python with full user-level access, and this node extends that to installing arbitrary things from a workflow. ComfyUI Manager exists precisely because the community learned that unvetted auto-install paths are how machines get compromised. The node is genuinely useful for the author's intended use - sharing a workflow with its dependencies attached - but treat manifests from unverified sources the way you'd treat a .exe from a stranger. Read the JSON before you flip the switch.

    CategoryBoyo/Asset Management

    Inputs (2)

    NameTypeDefaultDescription
    json_fileCOMBO1 options: No JSON files found - add files to custom_nodes/Boyonodes/assetJsons/
    download_triggerBOOLEANfalse

    Outputs (1)

    NameTypeDescription
    statusSTRING