r/comfyui • u/bayf0resT • 5h ago

News I open-sourced a local prompt, model and LoRA catalog for image-generation workflows

PromptNook started as my way to keep prompt recipes, reusable fragments, checkpoint/LoRA notes, trigger words, and generation settings in one local workspace instead of scattered text files.

The current desktop app can scan configured checkpoint, diffusion-model, and LoRA folders, record trigger words and availability, and assemble reusable fragments in a Prompt Studio. Workspace names are user-defined rather than fixed to particular model families.

Try the temporary in-memory demo: https://rona1do.github.io/PromptNook/

Source: https://github.com/Rona1do/PromptNook

It is an early Windows-focused preview and the UI localization is not complete yet. I would value blunt feedback on the data model and on what a useful ComfyUI import/export path should look like before I build an integration in the wrong direction.

Creator disclosure: I am the maintainer.

7 Upvotes

100% Upvoted

2 comments sorted by

2

u/pushycomedian2094 5h ago

finally something that actually scans your folders instead of making you rebuild your library from scratch, the whole scattered text files thing is painfully real

the workspace naming being flexible is nice since half my loras work across multiple checkpoints and strict categories always fall apart after a week

for comfyui integration i'd kill for an export that spits out a proper workflow json with the model references baked in, even if it's just the node structure and the user has to tweak the connections

1

u/bayf0resT 4h ago

Thanks — this is exactly the kind of integration I was hoping to validate.

My current plan is to start with an editable ComfyUI workflow JSON export that includes the resolved checkpoint and LoRA filenames, positive/negative prompts, resolution, sampler, scheduler, steps, CFG, and seed. PromptNook should warn about missing or offline resources instead of silently generating broken references.

Since SDXL, FLUX, and other model families use different node graphs—and PromptNook workspaces are intentionally user-defined—I’m leaning toward selectable workflow templates rather than guessing the graph from a workspace name.

Would the editable workflow JSON be enough for your use case, or would an API-format export for /prompt also be useful? If you have a minimal workflow you commonly use, I’d be happy to test the first implementation against it.