Screw job history

[comfy-pr-bot]

Feature Idea

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

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 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: comfyanonymous/ComfyUI#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 by Unito

[jtydhr88]

The issue that custom extension trying to deal with should be fixed in #7098.
It is caused by media asset.

[levicki]

The issue that custom extension trying to deal with should be fixed in #7098. It is caused by media asset.

That’s good to hear, but I'd still like a way to fully disable job history and all its UI nagging.

The feature feels completely tacked on without any consideration for the existing UI. You already have a sidebar with buttons that open panels — so why put the job history button in the top-right corner, make it always on top, and impossible to hide or move? It makes zero sense. It’s a poorly thought-out feature and a sloppy implementation, especially since it doesn’t persist state.

Here’s what should be done:

• Put the damn button in the sidebar.
• Place it at the bottom so existing button order isn’t disrupted.
• Make the job history panel movable like the Run panel.
• Ensure elements inside don’t jump around and the panel doesn’t resize on its own.
• Put job progress bars inside the panel on an opaque background.
• Persist its state — position, size, visibility.

Finally, an option in settings to fully hide the feature would be massively appreciated. Right now it’s intrusive, distracting, and just plain bad UX.

[comfydesigner]

Thanks for the feedback, you brought up valid points.

job history button in the top-right corner
Our original thinking for the location of the queue panel was to put it in close proximity to the default location of the run button.

In the past, or even currently, what do you use to gauge progress? The bottom panel/console? rgthree's progress bar?

[mossmatrix]

I also HATE this progress bar. It needs to be able to be disabled from settings at minimum. I use rgthree which is great and minimalistic. This atrocity just wastes space and on mobile in particular makes the experience awful. There’s a running bug where textareas on mobile when being edited fly to the top of the screen. My workaround was to position nodes at the top of if I needed to edit a textarea. Now when I do that this atrocious loading bar gets toggled to be even larger instead.

I’m confused that you do in fact have at least one designer? The design of comfy is so inconsistent week to week that it’s like an intern is just yoloing changes haphazardly. Buttons move constantly and instead of fixing actual issues you create new ones with this insane nodes 2.0 garbage that break data contracts. I’m starting to feel like a fork of Comfy is needed for actual stability and focus on the UI not getting in the way of the actual goal of generative AI workflows

[808charlie]

May I chime in with support for the sentiment in this post.

I have zero use for the job queue.
My personal answer to comfydesigner's query above is that I have rgthree's nodes:

• I have a progress bar across the top of the screen
• I have a progress bar across the k sampler
• I have a terminal window.

Zero use for the Queue in top right, except I now HAVE to open to open it to cancel jobs because the red cross (stop current) and red square (stop pending) have both been removed (argh).

Rather fearful of nodes 2.0 ever being enforced. Nothing but praise for comfyUI and indeed front-end improvements to date, but recent updates seem to have gone slightly awry. There was the lost ability to close 'node properties' (obscured by top menu) (now fixed thanks), now the above issue, and I keep finding more e.g. the really random problems like 'copy/paste' pasting something entirely incorrect (not fixed, but I can see issue logged).

Again, really grateful for the work you folk do; sorry to whinge!

[levicki]

Thanks for the feedback, you brought up valid points.

Thanks for responding.

job history button in the top-right corner
Our original thinking for the location of the queue panel was to put it in close proximity to the default location of the run button.

Panel with Run button is movable, so I don't see how that was a good idea? I keep mine bottom middle of the canvas.

In the past, or even currently, what do you use to gauge progress? The bottom panel/console? rgthree's progress bar?

I just look at the last node in the graph which is usually sampler of some sort. Also, I generate one image at a time so when it shows in Preview or Save Image pane it's done.

I'd like to point out that I can get 1024x1024 image using those fast SDXL models in ~2 sec. In that time the progress just blinks and disappears so fast you can't read what it says (especially on transparent background with that fading) -- you don't even get to aim at the cancel button and it's gone. I could see the utility for people with slower cards and those who do batches and want to see total progress but for me the Stop button was right next to Run so if I wanted I could've reacted in time to stop generation.

When designing UI, you need to think about people who:

1. Have impaired vision (hard to see small text or elements with poor contrast)
2. Have peripheral vision sensitive to motion (this is what triggered me so much)
3. Have higher sensitivity to flickering elements (and this)
4. Can't disambiguate by color (different kinds of color blindness or reduced sensitivity)
5. Come from different ethnic background and have different ideas what icons mean than you (always provide text to solve that)

And finally, you always have to think that people use things differently than you do.

Hope that helps.

[signalstop]

It really does have the feel of someone that doesn't actually use ComfyUI is making random changes to the UI. The cancel button should always be visible. The change from Grey to Red of the cancel button is also a great visual queue that something is in progress. Someone working on the project needs to speak up and tell the new owners to at least read these threads.

[without-ordinary]

The volume of stuff being added that overlays and blocks the canvas in the new UI is very frustrating.

My preferred number of UI elements that overlay the canvas viewport is zero or entirely user configurable toolbars which can optionally be undocked and floated.