Comfy-Org
The recent UI update made simple actions more complicated
Is there an existing issue for this?
- [x] I have searched the existing issues and checked the recent builds/commits
What problem are you experiencing?
After the latest update, ComfyUI’s frontend started hiding a lot of settings that used to be right on the surface. Things that used to take one click now require opening an icon first and then digging into the Settings. More steps, worse experience.
Commonly used features should stay visible, not buried under layers of collapses. It might look fancier, but it’s less practical.
Could you consider bringing the frequently used settings back to where they were, or at least give users an option to disable the folding and keep the old behavior?
When does this problem occur?
After the latest update, ComfyUI’s frontend started hiding a lot of settings that used to be right on the surface. Things that used to take one click now require opening an icon first and then digging into the Settings. More steps, worse experience.
Commonly used features should stay visible, not buried under layers of collapses. It might look fancier, but it’s less practical.
Could you consider bringing the frequently used settings back to where they were, or at least give users an option to disable the folding and keep the old behavior?
How often do you encounter this problem?
Multiple times per day
How much does this problem affect your workflow?
Blocks me from completing tasks
Current workarounds
No response
Ideas for solutions (Optional)
No response
Additional context
No response
┆Issue is synchronized with this Notion page by Unito
Hi @next1foreal! I'm Dosu and I’m helping the ComfyUI_frontend team.
Yes, there are existing issues tracking this problem—users have reported that the recent UI redesign made common actions more complicated by hiding frequently used options behind menus or icons, requiring more steps to access them. Maintainers have acknowledged this feedback and plan to improve menu accessibility and restore some options in future updates, but there is currently no built-in toggle or setting to revert to the old UI or disable the new folding/collapsing behavior [#6408] [#5095].
There is a partial workaround: you can launch the frontend with an older version (for example, by adding --front-end-version Comfy-Org/[email protected] to your launch script), but this is not an in-app toggle and may not be suitable for everyone. The Comfy.UseNewMenu setting controls whether the new floating action toolbar is active or the legacy menu is shown, but it does not restore all previous always-visible settings or fully revert the UI changes.
Some features/settings are also missing in the new UI (like the "randomize" option for core nodes in Nodes 2.0), and maintainers plan to restore these in future updates [#6807]. If you need help with specific configuration or troubleshooting, let me know!
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
![dosubot[bot] avatar](https://avatars.githubusercontent.com/in/324583?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @next1foreal! I'm Dosu and I’m helping the ComfyUI_frontend team.
Yes, there are existing issues tracking this problem—users have reported that the recent UI redesign made common actions more complicated by hiding frequently used options behind menus or icons, requiring more steps to access them. Maintainers have acknowledged this feedback and plan to improve menu accessibility and restore some options in future updates, but there is currently no built-in toggle or setting to revert to the old UI or disable the new folding/collapsing behavior [#6408] [#5095].
There is a partial workaround: you can launch the frontend with an older version (for example, by adding
--front-end-version Comfy-Org/[email protected]to your launch script), but this is not an in-app toggle and may not be suitable for everyone. TheComfy.UseNewMenusetting controls whether the new floating action toolbar is active or the legacy menu is shown, but it does not restore all previous always-visible settings or fully revert the UI changes.Some features/settings are also missing in the new UI (like the "randomize" option for core nodes in Nodes 2.0), and maintainers plan to restore these in future updates [#6807]. If you need help with specific configuration or troubleshooting, let me know!
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
I really hope the option to place the toolbar at the bottom can be brought back. I don’t understand why the new version completely removed this option. At the very least, users should have the freedom to choose where the toolbar goes, instead of having that choice taken away.
Right now it can only be placed at the top or hidden, which removes a feature many users relied on. This change essentially takes away user choice for no apparent reason.
Having to move the mouse all the way to the top every time just to switch workflows is inconvenient. I’ve already gotten used to having the toolbar at the bottom. Some users might prefer it at the top, but others—like me—prefer it at the bottom. I think this choice should be left to the users.
You're right—recent updates removed the option to place the toolbar at the bottom. The only available choices now are to show it at the top or hide it entirely. This was a deliberate change: the settings code explicitly migrates any old "Bottom" or "Floating" toolbar values to "Top", and there’s no hidden config or workaround to restore the bottom placement in current versions [coreSettings.ts].
Maintainers have said the new layout (with tabs and toolbar at the top) is meant to improve navigation for users with lots of tabs and to make the UI more scalable and future-proof, but many users have voiced the same concerns you have about lost flexibility and workflow disruption [#5095]. There’s no official plan or timeline to bring back the bottom option or make toolbar placement configurable, though some users have suggested making all toolbars dockable to any edge [#6104].
If you need the old behavior, the only workaround is to run an older frontend version, but that comes with its own trade-offs. For now, all logic funnels through the top-only setting, and user choice for toolbar placement isn’t supported [#6408]. If you want to keep up with any changes, following those linked issues is your best bet.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
Removing the stop button to hide it under the queue tab is crazy work, I don't see the point of doing that, this is bad
I agree with this post, please stop pushing such radicals UI changes without the having the option to leave it as it was, don't you guys test with other users before updating this kind of stuff, it's baffling
I drastically hate the new top floating toolbar. This is a lot of dead wasted space in the tab bar even with many workflows open. With everything now forced to the top of the screen and the floating panels, the new UI feels far more crowded despite all the removed functionality.
Also to note, it is seemingly no longer possible to revert only the frontend version. Comfyui backend 0.3.73 will not function with frontend version that is not the current recommend 0.30.6. Reverting the front end back to previously recommended frontend of 1.28.9 results in an error and a non-functional and corrupted UI.
After I'm don't testing Flux2 tonight, I'm reverting my Comyui installs back to 0.3.71. I was able to mostly tolerate that UI.
Why does every UI/UX designer always make things more complicated?
Canceling a job should be as easy as clicking the cancel button. But now I’m forced to hover over the top-right corner, wait for the dropdown animation to appear, and then click the cancel button. SMH.
Is it really that hard to keep the cancel button on the floating panel while adding a second cancel option anywhere you want?
@muljanis45 Hey, totally understand and relate to your frustration. That being said, being angry will not fix the issue quicker (unless you're an angry dev, then things can be done faster lol).
While devs figure out how to best fix this issue, you can stick to the frontend version 1.32.9. It is one version before the removal of the button and was still compatible with the latest version of the backend last week when I pulled it.
Also, I saw they released 1.32.10 yesterday along with 1.33.10 today, are they maintaining both 1.32 and 1.33 in parallel? I haven't tried 1.32.10, but might work as well.
@muljanis45 Hey, totally understand and relate to your frustration. That being said, being angry will not fix the issue quicker (unless you're an angry dev, then things can be done faster lol).
While devs figure out how to best fix this issue, you can stick to the frontend version 1.32.9. It is one version before the removal of the button and was still compatible with the latest version of the backend last week when I pulled it.
I get that being angry won’t fix anything faster, but It’s not a technical issue that needs a fix, it’s a design choice that actually made the user experience worse. They removed a cancel button that had been there from the beginning, thinking it would make things simpler, but it really had the opposite effect.
It’s been a week, and it feels like none of the Comfy devs have even checked this issue. What if they just leave the design as it is, just because it was their decision in the first place?
Rolling back to an older version is a temporary workaround, sure, but it doesn’t address the actual UX problem.
@muljanis45 Yeah no worries, I'm with you on that 👍 I really hope they address this issue. @christian-byrne added the "design" tag and they have not closed this issue yet, indicating they are aware of it and will probably fix it in the coming weeks.
I just wanted to emphasize that version 1.32.9 for the frontend is a good temporary workaround for now, since I didn't see anyone mention it.
is it possible to restore old job history reel? i now have to have keep open both tiny job history on the upper right and assets reel on the left. and functionality is worse. also the top toolbar now takes more space. there is less and less useful workspace now, cramming the interface. ergonomics has gotten worse!
Ah, nevermind about sticking to a previous version. 1.33.10 is now required, which is a few versions after the version where the buttons were removed from the floating panel.
https://github.com/Comfy-Org/ComfyUI_frontend/pull/6723
So this is the commit that separates the Run and Cancel buttons? This is kinda crazy… please add an option to at least revert it or keep the Cancel button docked with the Run button. I always update Comfy whenever there’s a new commit, so now i’m basically forced to use this UI version
For me, Right now the approach just feel doesn’t make sense. The floating Run button can be dragged anywhere, but the Cancel button is fixed in the corner, and i believe most of users move the Run button somewhere else on the canvas, so they end up far apart.
Unless you make the Run button fixed in the top-right near the job history (and not movable)...this change just doesn't make sense
It’s like having a car where the gas pedal is under the driver’s seat, but the brake pedal is over on the passenger side...
In v1.35.0, the button it back again, but is still detached from run and is now a big annoying red box.
Thanks @without-ordinary for the info, it's good to have a static, visible cancel button. However, the pop-up still shows up when I go near the upper right part of the canvas. Is there a way to disable it so that I don't keep accidentally hitting the suddenly appearing, now redundant cancel button on it when trying to select a node in that area?
