Tag Data Loader (Derpibooru)

This node loads a previously saved Derpibooru tag collection by name, so you can feed it back into the Derpibooru source node instead of re-running the live search that produced it. It's deliberately minimal - a single dropdown, a single output - and it's meant to be paired: it does nothing useful on its own, but wired into the source node's optional input, it turns a one-off query into a reusable, offline tag pool you can draw from any time.

Why you'd reach for it

Derpibooru is the tag source the README itself recommends first for Pony Diffusion - "Derpi is preferred" over e621 for that model family. If you've dialed in a Derpibooru query that reliably returns the character, style, and quality of tags you want for a Pony gen, that's worth locking down rather than re-rolling on every session. Re-querying live means a different result set every time (images get added, filters can shift what's visible, the network call itself takes time); saving the pull once and loading it back with this node gets you the exact same tag pool on demand, with no API round-trip.

It's also the practical workaround if you're relying on Derpibooru's default system filter rather than a personal API-key filter: lock in a good pull while it's fresh, and you're not dependent on re-searching under the same filter conditions later.

The inputs and outputs that matter

One field: collection_name, an enum dropdown listing your saved Derpibooru collections. It starts empty - there's nothing to list until you've saved a collection at least once with Tag Data Saver. That's expected, not broken.

The output, tag data, is typed LPP_TAG_DATA_DERPIBOORU, matching exactly what the Derpibooru source node's optional tag_data input expects. Wire the two together, leave send_request off on the source node, and it draws prompts from your saved collection instead of hitting Derpibooru's API. You're still free to change the source node's format (EasyFluff, EasyFluff no artist names, or Pony Diffusion V5(.5)/V6) or prompt_template against that same loaded data without needing to re-fetch anything.

How to install it

No separate install - this comes bundled with the whole Lazy Pony Prompter pack. ComfyUI Manager: search "Lazy Pony Prompter," install, restart. Manual clone:

cd ComfyUI/custom_nodes
git clone https://github.com/Siberpone/lazy-pony-prompter

Restart ComfyUI afterward. No models to fetch, no heavy dependencies - it's a thin API client bundled with the rest of the LPP nodes. You'll find this one under the LPP/loaders category alongside its Danbooru and E621 siblings.

Common issues & troubleshooting

Dropdown is empty. The most common point of confusion, and not a bug: nothing has been saved yet. Run Derpibooru with send_request on, route its LPP Tag Data output into Tag Data Saver, name it, and this dropdown fills in.

Wrong collection loaded. If a save name got reused, check the Saver's overwrite setting - a name collision either silently overwrote the earlier save or was rejected, depending on that flag.

Connection won't snap. This node's output type (LPP_TAG_DATA_DERPIBOORU) only matches the Derpibooru source node's tag_data input - it's a different type from Danbooru's or E621's loader outputs, and different again from what Tag Data Saver expects on its own input (the generic LPP_TAG_DATA, produced by the source node's main output). A refused wire is almost always a type mismatch.

Limited to system filters. This is a limitation of what you saved, not the Loader: if the original pull used Derpibooru's default system filter rather than a personal API-key filter, that's baked into what you're loading back. The README documents personal-filter API key setup for the A1111 side only; it isn't spelled out for ComfyUI.

General roughness. Per the README, the ComfyUI nodes are "somewhat experimental and may have some bugs," with UX compromises made to fit ComfyUI's interface. Minor friction here is an acknowledged tradeoff, not a sign of misconfiguration.