Never Lose A Good Prompt Again With Comfyui-PromptHistory

    
        By vramkickedin    
     | 
    
            June 28, 2026 at 2:50 pm        
    
     | 
    
        2 min read

Comfyui-PromptHistory is a new ComfyUI extension that adds two convenient nodes for saving every prompt you use during image generation. It stores those prompts in plain JSON files, making them searchable, reusable, and even batch-queueable right from the node. The extension also offers optional CLIP encoding so it can replace a standard text encode node directly.

Developer Dawncreatescode who also created Comfyui-Pin-Node-Input built this tool to solve the simple but common problem of losing a great prompt after a session. Prompts are saved automatically in a persistent history that survives ComfyUI restarts, and duplicate entries are merged while a hit counter tracks how often you reuse each one. This gives you a growing, searchable library that you can organize into separate files for different projects or styles.

Persistent prompt history and search

Key Features

Persistent history saved to JSON files.
Multiple files for project-based collections.
Real-time search with regex support.
Three modes: edit, random, sequential.
Duplicate merging and hit counter.
Batch queue prompts for back-to-back runs.

Anyone who regularly generates images with ComfyUI and wants to keep track of effective prompts will find this extension useful. It helps you revisit old ideas by randomly or sequentially cycling through past prompts, and the batch queue feature lets you test multiple prompt variations without manually setting up each run. Artists and tinkerers who manage different projects can also separate prompts into distinct history files for easier organization.

What the developer notes about storage

Since prompts are stored as plain text on disk, you should be careful about sharing history files publicly or committing them to a public repository. The default save location sits inside the node folder, but the developer recommends moving it outside of custom_nodes if you expect to reinstall the extension from scratch often. A maximum of 500,000 entries per file keeps the history from growing too large.