[GH-ISSUE #289] [Feature Request] Dynamic Tag List Switching #200

New issue

Open

opened 2026-10-30 21:20:54 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-30 21:20:54 +00:00

Owner

Originally created by @AviceProjects on GitHub (May 31, 2024).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/289

Originally assigned to: @DominikDoom on GitHub.

Allow dynamic tag list switching based on the current model. (For example, if I am using an anime model, but switch to a furry model, I'll want my tags to switch from Danbooru tags to e621 tags)

Originally created by @AviceProjects on GitHub (May 31, 2024). Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/289 Originally assigned to: @DominikDoom on GitHub. Allow dynamic tag list switching based on the current model. (For example, if I am using an anime model, but switch to a furry model, I'll want my tags to switch from Danbooru tags to e621 tags)

bsakaguchi added the

enhancement

label

2026-10-30 21:20:54 +00:00

bsakaguchi commented

2026-10-30 21:20:55 +00:00

Author

Owner

@DominikDoom commented on GitHub (Jun 1, 2024):

Model switching detection based on name or hash is already a thing due to the black/whitelist feature, so it's not hard to expand per se.

The issue is more that I am unsure of how to let the user enter the mapping in a good way using the settings UI, which is also why I haven't added it so far.
Gradio support/UI for multi-line text fields is pretty bad, except with code blocks, which I use for the keybinds and color mappings.
What I don't like about these is that the JSON format I need there requires the user to enter syntactically correct key-value pairs, which is ok for predefined stuff like keybinds but could be an issue if the user has to enter it from scratch. Maybe a simple csv style input would be better for this case here, although it would also be a bit harder to parse from the settings input.

Any opinions on what you would prefer?

@DominikDoom commented on GitHub (Jun 1, 2024): Model switching detection based on name or hash is already a thing due to the black/whitelist feature, so it's not hard to expand per se. The issue is more that I am unsure of how to let the user enter the mapping in a good way using the settings UI, which is also why I haven't added it so far. Gradio support/UI for multi-line text fields is pretty bad, except with code blocks, which I use for the keybinds and color mappings. What I don't like about these is that the JSON format I need there requires the user to enter syntactically correct key-value pairs, which is ok for predefined stuff like keybinds but could be an issue if the user has to enter it from scratch. Maybe a simple csv style input would be better for this case here, although it would also be a bit harder to parse from the settings input. Any opinions on what you would prefer?