Would ComfyUI-PromptRandomChoice be acceptable for ComfyUI-Manager?

[ruminar]

Hi, I made a small ComfyUI utility node:

https://github.com/ruminar/ComfyUI-PromptRandomChoice

ComfyUI-PromptRandomChoice randomly selects one item from a prompt candidate list on each execution.

It is useful for varying prompt elements such as:

• background
• time of day
• weather
• situation

Main features:

• split candidates by actual newline or |
• trims leading/trailing commas and spaces
• outputs prompt text like ,coffee shop,
• supports change_every
  • 1: choose every run
  • 3: keep the same choice for 3 runs
• supports repeated candidates for simple weighting
  • example: day|day|day|sunset|night
• displays the current choice in the node title
• no external Python dependencies

I am considering submitting a PR to add this to custom-node-list.json.

Would this kind of small utility node be acceptable for ComfyUI-Manager?

Also, I have a few other small independent ComfyUI utility nodes.
Would it be better to submit them separately, or combine them into one utility pack?

I understand that the final decision may depend on reviewing the repository itself. I would appreciate guidance on whether this should be submitted as an individual node, or whether small utility nodes like this should be combined into a utility pack.

[ruminar]

For additional context, these are the related small utility nodes I currently maintain:

ComfyUI-LightQueueCounter

A small node for roughly understanding the total number of queued jobs, including jobs already sent to the backend, when more than 200 items are queued.

Recent versions of ComfyUI split queue handling between the frontend and backend for performance reasons. As a result, it becomes difficult to understand the total queue size once it exceeds 200 items.

This is probably something that would ideally be supported by ComfyUI itself. However, if very large queues are not a priority for the official UI, support for this may be delayed. That is why I created this node.

ComfyUI-CheckpointNameCycler

A node for trying many checkpoints in bulk, especially the ones that have been sitting unused on my SSD.

The selected checkpoint name can be included in the output filename, so by simply running overnight image generation, it becomes easy to collect and manage style samples for many checkpoints.

ComfyUI-CheckpointWidgetRefresh

A small UI node that synchronizes checkpoint-related selection lists with the current file state, without restarting ComfyUI.

This is especially useful when organizing checkpoints while reviewing images generated with ComfyUI-CheckpointNameCycler.

It updates the widgets and related node lists together while keeping consistency with ComfyUI’s internal checkpoint list management, allowing checkpoint management without restart.

ComfyUI-PromptRandomChoice

A node intended to create more varied images by switching background, time of day, weather, and other situational prompt fragments.

This is also useful when evaluating checkpoints, because it helps generate a wider variety of images before making decisions about which checkpoints to keep.

---

All of these nodes were designed to be lightweight and to avoid dependencies on other libraries, so they should have minimal impact on overnight batch generation speed.

Another shared design characteristic is that each node updates its own node title to display its current state, so that it is easy to understand what the node is doing while a workflow is running.

Because this behavior is consistent across the nodes, if it would be preferable to combine them into a single utility pack rather than submitting them separately, I am open to that approach as well.

Thank you for your consideration.

[ruminar]

It looks like these nodes have now been automatically registered separately, so I will close this question.

Thank you for your time.