category:Ideas Custom model QoL improvement by automation

[sharp-trickster]

Every custom model have a "activation word" and a sampler in which it was trained, and everytime I load a custom model I have to google it on huggingface and check the model description for these values in order to use it.

My suggestion:
We scrape huggingface models to create a table of values: We can ID the models by their signature, so the filename on the drive doesnt matter, and then we have the right sampler be selected when the model is loaded, and the keyword be presented on the interface on the prompt or something, maybe even sub it for a placeholder like "KEYWORD" so it works on every model, then a prompt preprocessor switch the placeholder for the model keyword internally before diffusion everytime you click "generate".

Down the line, even a fullblown managing interface (like the one we now have for scripts) with an updated list of models would be super nice to have, but, for now, just this thing I described above would make a great improvement in quality of life IMHO.

Thanks.

[ClashSAN]

there seems to be a test for keyword extension: https://github.com/mix1009/model-keyword
you may want to work on it with the presets extension: https://github.com/Zyin055/Config-Presets