Comfy-Org / Comfy-Org/ComfyUI_frontend

Screw job history

Open
#7,107 26 comments 11 reactions 0 assignees View on GitHub
area:ui Design Feature
Dominant language
TypeScript
Stars
2k
Forks
699
Avg merge
1d 7h
Merged PRs (30d)
490

Description

### Feature Idea

I don't know whose idea it was to add this without an OBVIOUS option to DISABLE it:

Image

I am sure there are people who enjoy overlays, progress bars, and popups — I certainly don't, and I would really appreciate an option to kill this with fire, nuke it from orbit and never ever see it again on the canvas. And please don't bother telling me to "Just ignore it" — that's not an option.

When we are at it, why not also have an option to FULLY DISABLE job history and all related stuff for those who don't use it? Right now we can only reduce queue to 2 items and it is still causing performance issues that people wrote [an extension](https://github.com/SparknightLLC/ComfyUI-DisableJobHistory) to stop it.

Finally, sorry if this sounds like a somewhat rude rant but blinking stuff in my peripheral vision seriously triggers my OCD. And yes, it's pretty much blinking on RTX 5090 — progress and the option to cancel it just flashes and disappears so it's totally, utterly pointless.

Thanks for considering it.

**EDIT:** A minimal acceptable quick workaround would be if the "View Job History" persisted its state (shown, hidden) so if I clicked to hide it it stays hidden instead of popping up on next queue run.

### Existing Solutions

_No response_

### Other

_No response_

---

*This issue is transferred from: https://github.com/comfyanonymous/ComfyUI/issues/11056*

Original issue was created by @levicki at 2025-12-02T21:20:11.000Z

**Original Comments:**

@m8rr:

This is probably an issue with https://github.com/Comfy-Org/ComfyUI_frontend

but I agree with your opinion.

┆Issue is synchronized with this [Notion page](https://www.notion.so/Issue-7107-Screw-job-history-2bd6d73d365081028549eefdd8a58ee7) by [Unito](https://www.unito.io)

Contributor guide

Open the contributing guide

Research direction

No file or test is named. Start by locating the frontend entry points for job history, queue progress, overlays, and the View Job History control, then review the discussion to narrow the requested scope. Done means an agreed, tested way to disable the related UI or persist its hidden state without the reported performance impact.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.