Asset Manager

Drop Asset Manager onto the canvas and nothing happens. That's not a bug: the node is a zero-input, zero-output stub whose whole job is to exist so the pack registers itself. The real work lives in a menu-bar button called Asset Manager plus a set of API routes that hook into ComfyUI's own server when it starts. It's not a Save Image replacement and it never sits in your pipeline. It's the front door to Lumin, a cloud workspace for browsing, commenting on, and reviewing the images your team generates.

The pitch, straight from the author: you and your team crank out images in ComfyUI for moodboards and concepting, they pile up as _1_final_1.png in local folders, get shuffled through Google Drive and WhatsApp, and nobody can find anything. Lumin gives you a shared workspace with projects, a board view, statuses and comments - and this pack is the pipe that gets your outputs there, workflow metadata included.

How it works

The Python node is deliberately boring. AssetManagerNode.process() returns an empty tuple; there are no inputs and no outputs. All the machinery is web/assetManager.js talking to custom routes registered on PromptServer, so there's no separate service to run. Open the Asset Manager modal and it calls /asset-manager/get_output_images, which walks your ComfyUI output folder recursively and lists everything from PNGs to MP4s to GLBs, newest first. Select what you want, delete junk straight from the list, and hit upload.

The upload itself is the meaty part: a multipart upload that splits files into 10MB chunks (create → part → complete, with an abort fallback) against Lumin's upload API, with your workflow JSON attached as metadata. That metadata bit is the whole reason this exists. ComfyUI already embeds the workflow in every PNG - Lumin parses it back out so teammates see the prompts, models, and params without digging into the file. There's also an Automatic mode that watches the output folder and pushes new files without you clicking anything.

The inputs and outputs that matter

• Inputs: none
• Outputs: none

info_schema is empty on both sides. This is not a data node - don't try to wire it into anything and don't expect a "done" signal. If you've dragged it onto the canvas and see nothing, close the graph and look at the menu bar instead.

Install

ComfyUI Manager (search "ComfyUI-Lumin-Upload"), or the old-fashioned way:

cd ComfyUI/custom_nodes
git clone https://github.com/theluminhub/ComfyUI-Lumin-Upload

then restart ComfyUI. That's the entire install: requirements.txt is a single line (requests>=2.31.0, which ComfyUI ships anyway) and there are zero model downloads. One of the lightest packs you'll install this month.

Setup - the part people bounce off

No key, no function. You need an account on luminhub.io and an API key. Then, in the Asset Manager modal's Settings tab: paste the key, pick your organization, and in the Main tab choose a project plus Manual or Automatic mode. Until key, organization, and project are all set, Automatic mode silently does nothing - the UI does warn you, at least.

Gotchas worth knowing

• Your workflow JSON goes to their servers. The author is upfront that Lumin parses it for display and planned search, and it can include model paths and prompts you'd rather not share. The r/comfyui announcement thread drew real pushback on exactly this - "an API just so I can save my own assets" is a non-starter for privacy-minded people. Manual mode at least guarantees nothing leaves unless you click.
• The endpoints say nodehaus.io, not luminhub.io. Poke the network tab and you'll see api.upload.nodehaus.io - same service, the README just shows the friendly domain. Don't get spooked mid-debug.
• It's a young, bare-bones project. The README is four short paragraphs and it's aimed at teams. For a solo user this is a lot of setup to move files you could script in five lines; where it shines is giving a small team one shared surface to review each other's output instead of a folder of _final_v3.pngs.

Last thing: for one person on one machine, I'd pass. For a team drowning in outputs with no review process, this genuinely solves a problem nobody else's node stack does.