Skip to main content

Open Manager for ComfyUI Open Manager ComfyUI PyPI License Donate Security: SkillsLLM

Open Manager for ComfyUI

Open Manager for ComfyUI: a quick tour, on YouTube

Download Manager
Download Manager
Model Library
Model Library
Resource Monitor
Resource Monitor
Desktop Mode
Desktop Mode

The whole workspace at once: one screenshot.

A manager for the whole ComfyUI workspace, not just its nodes.

Packs Browse the Comfy Registry, install from registry or GitHub, see what an install does before it runs
Workspace Models on disk, downloads, memory, outputs, and your own files
For remote ComfyUI instances A desktop on a tab of its own. No swapping between tools just to view outputs, or manage files
Off by default The monitor strip and Desktop Mode
Never A node in your graph. Nothing is installed or built at load time

Open Manager is not affiliated with ComfyUI-Manager or the Comfy Registry.


Install

Two ways. Only the first gives you ComfyUI's Extensions button: ComfyUI draws it when it finds a manager package in its own Python at startup, before any custom node loads.

As the manager As a custom node
Installed with pip, into the Python ComfyUI runs on git clone into custom_nodes, or from ComfyUI-Manager or the Comfy Registry
Opens from Extensions, and the Discovery sidebar tab The Discovery sidebar tab
ComfyUI-Manager Replaced. A ComfyUI-Manager folder in custom_nodes is skipped Left as it is
Launch flag --enable-manager None

As the manager

Windows portable build. In the ComfyUI_windows_portable folder, the one holding python_embeded and run_nvidia_gpu.bat, run:

python_embeded\python.exe -m pip uninstall -y comfyui-manager
python_embeded\python.exe -m pip install comfyui-open-manager

Then open run_nvidia_gpu.bat (or run_cpu.bat) in a text editor and add --enable-manager to the end of the line that starts .\python_embeded\python.exe -s ComfyUI\main.py, after the flags already on it:

.\python_embeded\python.exe -s ComfyUI\main.py --windows-standalone-build --enable-manager

Save it, and start ComfyUI with that file. A whole launch file, with switches and keys, is under Launch files.

venv, conda or a manual install. With the environment ComfyUI runs in activated:

python -m pip uninstall -y comfyui-manager
python -m pip install comfyui-open-manager
python main.py --enable-manager

With uv, uv pip uninstall comfyui-manager and uv pip install comfyui-open-manager. Pack requirements then install through uv too.

Check. At startup the console shows [Open Manager] enabled in place of ComfyUI-Manager, and Extensions opens Open Manager.

If Then
The console says the comfyui-manager package must be installed first The install went into a different Python. Run it again with the exact python.exe path that message prints. Do not run the manager_requirements.txt command it suggests: that installs the official ComfyUI-Manager instead
pip answers Requirement already satisfied and that message stays Add --force-reinstall --no-deps to the install command
The official manager opens Both packages own comfyui_manager, and it was installed again. On a portable build Open Manager still loads; elsewhere uninstall it and install Open Manager again
An Open Manager folder is still in custom_nodes from an earlier install Delete it, so one copy runs

As a custom node

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/open-manager-comfyui.git

Restart ComfyUI and open the Discovery tab in the sidebar. The console shows routes registered below /open_manager/v1/api.

On Vast.ai

An image of Vast's own ComfyUI with Open Manager as its manager, ComfyUI-Manager kept out, and Desktop Mode and file writes on. The template and how to use it: VASTAI.md.

Updating and logs

As the manager python -m pip install --upgrade comfyui-open-manager, with python_embeded\python.exe in place of python on a portable build
As a custom node git pull in its folder
From Open Manager Open Manager Settings compares this copy with pyproject.toml on GitHub, then updates and restarts: pip as the manager, git pull as a clone, the GitHub archive as any other custom node, swapped in only once it is unpacked. Needs installs and GitHub left on
Log --enable-manager writes user/comfyui.log, rotating to comfyui.prev.log and comfyui.prev2.log. OPEN_MANAGER_NO_LOG=1 leaves it alone

Access keys (optional)

Keys come from environment variables only. Access keys in the Open Manager menu shows which are set and by which variable.

For Variables Get one at
Gated and private models HF_TOKEN, HUGGING_FACE_HUB_TOKEN, OPEN_MANAGER_HF_TOKEN huggingface.co/settings/tokens
Starring, higher rate limit GITHUB_TOKEN, GH_TOKEN, OPEN_MANAGER_GITHUB_TOKEN github.com/settings/tokens
Scanning an install VIRUS_TOTAL_KEY, VIRUSTOTAL_API_KEY, OPEN_MANAGER_VIRUSTOTAL_KEY virustotal.com/gui/my-apikey

The value is the key itself: set HF_TOKEN=hf_xxx on Windows, export HF_TOKEN=hf_xxx on Linux and macOS, in the file that starts ComfyUI. See Launch files.

Starring needs a GitHub token that may read and change stars: a fine-grained token with the Starring account permission set to read and write, or a classic token with public_repo. Without one, a pack page shows its star count only.


Packs

Installing packs tutorial, on YouTube

Every version Flagged, withheld and banned included
Before you install Findings, dependency changes, new nodes, hardware fit
Contents named Binaries, pickles, wheels, bytecode
Licences Per pack, sortable
Your own repos By URL or owner/repo, kept in user/
Any ref Branch, tag or commit
Optional requirements Each group a pack offers, or all of them, after it installs or from its page, with the same dependency check as an install; an update that leaves a chosen group short offers it again
Workflow gaps Missing nodes, and which pack won a duplicate name
Import failures Each failed pack's error from ComfyUI's log, its traceback a click away
Workflow packs Each pack the open workflow uses, with node ids to copy
Folders and tags Installed packs grouped in folders of your own and tagged, from a pack's menu; #tag in the search lists a tag's packs
Every custom_nodes folder Packs in each custom_nodes path extra_model_paths.yaml adds are listed and managed where they are; new installs go to ComfyUI's first
Themes Gradients, icons, backdrops
Fast sync Whole registry in seconds

Findings reword the confirmation. A registry ban blocks Install until Install versions the registry has banned is on. A pack that asks for a ComfyUI major version above yours, such as the >=1.0.0 pyproject templates carry, is not reported as incompatible.

Beyond packs

Five pieces. None of them adds a node to your graph.

Default
OM Nodes Nodes 2.0 at classic node sizes and layout, switched from the ComfyUI menu off
Download Manager Fetches the models a workflow needs: resumes, verifies, picks the drive on
Model Library What is on disk across every registered folder: duplicates, unreferenced files, storage, and ComfyUI-Manager's model list to fetch from on
Resource Monitor CPU, RAM, VRAM and temperatures in ComfyUI's control bar, with a Memory panel behind it strip off, Memory button on
Desktop Mode Files, notes, outputs and programs on a tab of their own off, and needs OPEN_MANAGER_ENABLE_DESKTOP=1

Every panel opens as a movable window, or centred on the page. One setting each.

Remote installs

Desktop Mode is served by ComfyUI's own server: no second port, no second login. On Vast.ai, VASTAI.md has an image with it switched on.

Server switches

Environment variables, read once when ComfyUI starts. 1 turns a switch on. 0, or leaving it out, keeps the default. Set them in the file that starts ComfyUI, as in Launch files, and restart after changing one.

What ships on is closed with a NO_ switch:

Variable =1 =0 or not set
OPEN_MANAGER_NO_INSTALL Packs cannot be installed or removed Packs install and remove
OPEN_MANAGER_NO_GITHUB GitHub repositories cannot be added or installed They can
OPEN_MANAGER_NO_DOWNLOADS Models cannot be fetched They can
OPEN_MANAGER_NO_RESTART Open Manager cannot restart ComfyUI It can
OPEN_MANAGER_APPROVED_ONLY Only versions the registry lists as active install. No GitHub repositories Flagged versions and GitHub repositories install too

What ships off is opened with its own:

Variable =1 =0 or not set
OPEN_MANAGER_ENABLE_DESKTOP Desktop Mode can be switched on in the settings Desktop Mode is hidden
OPEN_MANAGER_ENABLE_FILES The file browser can be switched on in the settings The file browser is hidden
OPEN_MANAGER_FILE_WRITES The file browser renames, moves, copies and deletes files, makes folders, and saves text files and pictures. Media Assets can delete output files The file browser only reads
OPEN_MANAGER_ALLOW_BANNED Versions the registry has banned install, whatever the setting says The setting decides
OPEN_MANAGER_REPO_DOWNLOADS Whole Hugging Face repositories in ComfyUI-Manager's model list download, configs included Only single model files download

The server refuses what a closed switch governs and names the variable. Desktop Mode and the file browser are hidden rather than refused, and their settings do nothing until the machine opens them.

Launch files

Each variable goes in the file that starts ComfyUI, above the line that runs it. These open Desktop Mode and the file browser, give a Hugging Face key, and start ComfyUI with Open Manager as its manager. As a custom node, leave out --enable-manager.

Windows portable. run_nvidia_gpu.bat, in the ComfyUI_windows_portable folder. No spaces around =.

@echo off
cd /d "%~dp0"
set OPEN_MANAGER_ENABLE_DESKTOP=1
set OPEN_MANAGER_ENABLE_FILES=1
set HF_TOKEN=hf_xxx
.\python_embeded\python.exe -s ComfyUI\main.py --windows-standalone-build --enable-manager
pause

Linux and macOS. run.sh, in the ComfyUI folder. venv is the folder your environment is in; drop that line if python already is ComfyUI's.

#!/usr/bin/env bash
cd "$(dirname "$0")"
source venv/bin/activate
export OPEN_MANAGER_ENABLE_DESKTOP=1
export OPEN_MANAGER_ENABLE_FILES=1
export HF_TOKEN=hf_xxx
python main.py --enable-manager

Run chmod +x run.sh once, then start ComfyUI with ./run.sh.

A list is one value, comma separated: set OPEN_MANAGER_MODEL_HOSTS=civitai.com,cdn.civitai.com. The lists are in DOWNLOADS.md.


Reference

Where it appears

Interface Way in
Current A sidebar tab
Legacy menu (Settings -> Comfy -> Use new menu -> Disabled) An Open Manager button on that menu
Where it replaces the manager The top menu's Extensions button as well

Extensions follows ComfyUI: the panel on the modern interface, the classic menu of destinations under --enable-manager-legacy-ui. Override it under What the Extensions button opens. Both carry every destination, and the sidebar tab is unaffected.

ComfyUI's own manager links, such as the missing-nodes panel's, open the same place. Turn on Use ComfyUI's Nodes Manager to have them, and Extensions, open ComfyUI's Nodes Manager instead. Every install it starts is still run by Open Manager. So are the Install buttons ComfyUI shows for missing nodes, whichever is set.

Quality of Life Patches fixes faults in, and adds to, ComfyUI's own interface from Open Manager, each with its own switch and links to the issues it answers. A patch that finds ComfyUI changed, or already fixed, stands down and says so in the browser console.

Patch Default Effect
Media Assets keep generation time On Runs write their generation time, node and subfolder onto their assets
Media Assets open workflows from files On A job no longer in history opens the workflow saved in its file
Media Assets show files found by scans On Files an asset scan adds appear in Media Assets
Asset scans In their own process Where ComfyUI catalogues models, input and output. Alongside the server is ComfyUI's own: a long scan, such as the first one on a large library, slows the server until it ends, the first page load most. Before the server starts holds ComfyUI's startup until the startup scan ends. In their own process runs every scan in a hidden process at below-normal priority, which quits after five idle minutes. Scans stay in ComfyUI's process where that process would not see the same folders and database, such as when a node pack changes how model files are listed
Media Assets delete files Off Deleting an output also deletes its file. Needs OPEN_MANAGER_FILE_WRITES=1
Ask before downloading template media On Opening a template offers the media files it is missing, with Download and Ignore, in place of ComfyUI downloading them into input. Files already in input or temp are used, not fetched
Template media downloads Ask Always leaves ComfyUI to download a template's media as it opens. Ask turns on the patch above. Never fetches nothing; the Download Manager lists what is missing
Keep template media in input Off Template media downloads to input. Off, it downloads to temp, which ComfyUI empties when it restarts, and its nodes point at name [temp]. Turning it on moves the open workflow's files from temp to input and points its nodes there
Nodes Manager fits its contents On The Nodes Manager's frame fits its contents. On screens 3000px wide and over it otherwise cuts off the right side, close button and filters. Frontend 1.57 fits it itself
Subgraph nodes show promoted previews On A subgraph node on the classic canvas draws the latest preview promoted to it
Subgraph nodes keep their saved values On A subgraph node whose promoted widgets ComfyUI migrated loads with its saved values instead of the values they had at migration
Subgraph inputs and outputs move up and down On An input or output's menu inside a subgraph has Move Up and Move Down. Every node using the subgraph takes the new order with its links and promoted widgets, and Undo puts it back
Custom widgets follow their node's width On Custom and DOM widgets keep following their node once it has been shown in the properties panel
Nodes 2.0 widgets on the classic canvas On Curves, image compare and crop, video trim and crop, bounding boxes, colour palettes, the resolution preview and LoRA stacks work on the classic canvas, also when promoted to a subgraph. The painter, the compositor and light info show ComfyUI's own editors there. From frontend 1.58, curves and bounding boxes have undo and redo buttons, as on Nodes 2.0. Stands down when ComfyUI-Nodes2Classic is installed
Self-drawn widgets keep their size when zoomed On On Nodes 2.0, a widget that draws itself, such as a section header, draws at its node's width when it appears while zoomed in or out. Frontend 1.57 does this itself
Panels fit their node and scroll On On Nodes 2.0, a panel widget that sets its own height, such as a value readout, opens at that height, grows and shrinks with its node, and scrolls
Previews hold still at the canvas edge On On Nodes 2.0 in Firefox, a node with both a panel widget and an image preview, such as WAS Node Suite's Image Save, no longer flickers between two layouts while the preview meets the canvas edge
Node error and Enter buttons in the title bar On On Nodes 2.0, the Error, Issues, Enter subgraph and advanced inputs buttons sit in the node's title bar in place of tabs hanging below the node. A node left with room for the tab shrinks to its content once
Combo lists use the room on screen On On Nodes 2.0, a combo's list grows into the space on screen in place of about seven options
Combo lists open folders as submenus On On Nodes 2.0, a list of files kept in folders, such as LoRAs, shows each folder as a submenu. Typing in its search box searches every file
Image, video and audio pickers Grid with folders On Nodes 2.0, the picker on Load Image, Load Video, Load Audio and other upload combos. Grid is ComfyUI's. Grid with folders opens the folders in input and output, with small previews of pictures, and a Generated file in a subfolder loads from it. Typing in its search box searches as ComfyUI does. Plain list is a combo list, folders as submenus, with the upload button below it
Right-clicking a video opens the browser's menu On On Nodes 2.0 and OM Nodes, right-clicking a video on a node opens the browser's menu for it, with Save video as and Open video in new tab, in place of the node's menu
Image menu acts on the shown image On On Nodes 2.0 and OM Nodes, Open Image, Copy Image and Save Image in a node's menu act on the image the node shows. ComfyUI's do nothing while any image but the first is shown
Hide Partner nodes Off Paid Partner (API) nodes, their templates and the Login button are hidden
Node folders and tags On Folder and tags in a node's right-click menu, in the Node Library and on the graph. Folders are ComfyUI's own favourites folders. Tags show beside node names in the Node Library, and #tag in node search lists a tag's nodes. The classic Node Library gets the search only
Looping animations hold still while a job runs On Running spinners and pulses stop redrawing until the queue is empty
Links share one colour table per frame On Drawing a link no longer copies the colour of every link type from every pack, which costs most on large graphs with many packs installed
Go to Node by ID On Opens and frames a node by ID, or by a path such as 12:5 for node 5 inside subgraph node 12. In the canvas menu, and bindable under ComfyUI's keybindings
Middle-click does not paste On On Linux, a middle click no longer pastes the last copied nodes
Zip ties On Dragging across links with Z held ties them into a ribbon. With Shift held as well the tie is straight: horizontal, vertical or at 45 degrees. Dragging across a tie with Z held, or double-clicking it, removes it. Ties move by dragging, and turn by dragging with Alt held, in 45 degree steps with Shift. A straight or turned tie keeps its angle until Auto angle in its right-click menu, where its colour is also set. Links enter a tie in the order they arrive, keep it through every tie after, and cross only past the last one; they reorder as nodes move. Hovering a tie shows a dot for each link on its outgoing side; dragging from one connects that link's output to another input, and the new link leaves through the tie and the ties before it. After comfyui-zip-ties, whose saved ties it reads; stands down when that is installed
Hidden links as nubs On A hidden link shows a small nub in its type colour on each node's edge, in place of a type label. Hovering a nub shows the label; hovering the label shows the link
Selected nodes show their hidden links On While nodes are selected, the hidden links between them and the nodes they connect to are drawn, whether every link is hidden or only some
Selection box covers the whole drag On The box dragged to select nodes covers the whole drag while the job queue is open, in place of a line under the selection, and passes under the panels around the canvas. Frontend 1.60 does this itself
No frontend_only badge On Nodes with no Python side carry no source badge
Running and waiting jobs open as workflows On Open as workflow in new tab works on a job still running or waiting in the queue, and on that job once it finishes
API jobs open as workflows On Jobs queued with only an API prompt open as a laid-out workflow
Hide the workflow name box at the top level Off Up to frontend 1.36, the box naming the open workflow shows only inside a subgraph
Extension toolbox buttons show their names On A selection toolbox button an extension adds shows the name its extension gave it on hover
Workflow tabs without a scrollbar On The tab strip drops its scrollbar. Faded edges show where more tabs are, and the mouse wheel scrolls to them
Workflow tabs look like tabs On Flat tabs side by side with a line between each, the open one marked along its top, in place of rounded buttons
Bottom panel docked to the edges On The Logs and Shortcuts panel meets the sidebar and the window's edges, with square corners, in place of floating over the canvas
Custom palettes keep readable buttons On From frontend 1.58, a colour palette without its own theme colours no longer paints buttons and fields in its node header colour, where their text can be unreadable. They take a shade of the palette's panel colour
Bottom panel header has no frame On The header of the bottom panel, where Logs opens, draws only the line under it, without ComfyUI's 3px grey border on its other three sides
Node search narrows every match On In the node search box, a category or the Comfy, Partner or Extensions filter lists every match it holds, not only those among the top 64
Node search draws only the rows in view On Results build as they scroll into view
Node search waits for a pause in typing On Slow searches run once typing pauses
Use Everywhere finds nodes quickly On With Use Everywhere 8 on Nodes 2.0 or OM Nodes, its search of the page for every node on every frame is answered from the nodes already found, which takes back most of the frame rate it costs on large workflows. Stands down when Use Everywhere stops searching. Open Manager also says once, per Use Everywhere version, that it slows Nodes 2.0

Link style, under Settings -> Open Manager -> Links, draws the links between nodes on the classic canvas, Nodes 2.0 and OM Nodes. Links click, reroute, zip tie and carry their midpoint marker as with Solid.

Style
From the theme The active theme's links.style, or Solid. The default
Solid ComfyUI's own
Energy conduit A glowing core with pulses running from output to input
Flowing dashes Dashes running from output to input
Chain Interlocking links in the link's type colour
Rusty chain Speckled rust-brown links
Pipes Shaded pipes with a lip at each end
Fabric cord A braided cord, its weave pointing from output to input
Rope Twisted hemp
Beads Beads on a thread
Electric arc A flickering bolt

Link path sets where links run, in any style. Clicks, the midpoint marker and zip ties follow the drawn path.

Path
Link Render Mode ComfyUI's Spline, Linear or Straight. The default
Circuit board Traces with cut corners that run around nodes and each other, never under or over them. Links running close together gather side by side. Routes are laid again a moment after nodes stop moving
Physics Links hang under gravity and swing when a node moves

Ghost links fades each link along its own length a short way from the slots it joins, under a slowly drifting glow. A selected node's links show in full.

Link motion runs the moving styles, Physics swings and the ghost glow always, only while a workflow runs, or never. They redraw at up to 30 frames a second, less often when drawing takes longer, and not while the tab is hidden. Zoomed out, each style draws plainer.

Network

Open Manager reads the Comfy Registry live. What it contacts:

Host When
api.comfy.org Browsing and installing
cdn.comfy.org Downloading a registry version to install
codeload.github.com Downloading a GitHub repository to install
raw.githubusercontent.com Licences, READMEs, images
api.github.com Pack stats and gallery, branches, tags and commits, starring, licence lookup
pypi.org Checking for a newer Open Manager
www.virustotal.com Scanning an install, with a key
huggingface.co, github.com and their download hosts Model downloads. OPEN_MANAGER_MODEL_HOSTS adds others
Wherever a pack points Pack icons. README and gallery images given as absolute URLs, unless Read pack README and repository metadata is off

Settings

Under Settings -> Open Manager, and in Open Manager Settings from the Open Manager menu, the Start menu or the Open Manager: settings command. That window holds every Open Manager setting by section, and an overview: the version and updates, the system, the server switches, each patch's state, and which access keys are set. Installed as the manager, it also offers to uninstall the official ComfyUI-Manager where its package or a ComfyUI-Manager folder is still there, keeping the file that loads Open Manager.

Trust Answer once per author, or every time

A GitHub token, set as GITHUB_TOKEN, raises 60 anonymous calls an hour to 5,000. Without one, pack pages still show README, gallery and versions.

The registry address is BASE_URL in open_manager/registry.py, and BASE in open_manager/catalog.py for the offline copy. Both can point at a mirror or a private index.

Trust

Asked Before installing a pack from GitHub, loading a workflow from a pack, or downloading a model. Registry installs too, with Ask before installing a registry pack from an untrusted author on
Remembered in user/open_manager/trusted_authors.json
Never Hides a finding

Requirements

torch, torchaudio, torchsde and torchvision are never installed from a pack's requirements: they carry the build your ComfyUI was set up with. The check before an install reads the requirements.txt the install hands to pip. The install policy guards packages ComfyUI, an installed package or another pack uses: the default leaves them as they are, and the upgrade and downgrade choices let them move one way. A package only the pack itself uses changes as it asks under every choice. Anything held back is named in the check and in the install's issues, with what uses it.

A requirement whose PyPI release is NVIDIA's wheel stub installs from the index the stub names, pypi.nvidia.com or pypi.ngc.nvidia.com; a stub naming any other index is not followed. An install that has to replace a file the running ComfyUI holds open, as a loaded .dll is on Windows, can be queued for the next start, where it runs before any pack loads.

To substitute a package, map it in user/open_manager/pip_overrides.json:

{ "opencv-python": "opencv-python-headless>=4.9" }

Optional groups follow the same rules. The groups chosen for each pack are kept in user/open_manager/optional_requirements.json and forgotten when the pack is removed.

Your GitHub list

Add By URL or as owner/repo
Behaves like A registry pack: installs, updates, uninstalls
Written to user/open_manager/github_sources.json, outside the pack, so it survives an uninstall
Remove from list Delists and uninstalls in one step

For pack authors

Declare a [tool.open_manager] table in pyproject.toml and every Open Manager user sees it. Every field is optional. Packs without the table are unaffected.

Field Gives you
capabilities What your pack does, as its own panel on your page
release_note Your words above the version list, not a changelog guess
incompatible Name a package and version; users are warned before installing
source Say GitHub and the panel recommends it over the registry copy
themes Ship colour palettes with gradients, icons, backdrops and rulers
example_workflows Loadable from your page, with thumbnails
gallery Screenshots from your repo or elsewhere
docs, funding Buttons in your page header
[tool.open_manager]
incompatible = ["numpy>=2.0"]                   # declare known conflicts with other packages
source = "github"                               # prefer installing from the repository
branch = "main"                                 # named in the GitHub recommendation
docs = "https://example.com/docs"               # documentation URL
funding = "https://ko-fi.com/you"               # funding URL
release_note = "1.4.0 needs config regen."      # shown above the version list, 600 chars
capabilities = [                                # what your pack does, its own page panel
  "filesystem", "network", "subprocess",        #   from a fixed list, see below
]
example_workflows = ["workflows/*.json"]        # a path, a glob, or a directory
themes = ["themes/my-theme.json"]               # list themes to offer
gallery = [                                     # shown off on the pack page, up to 24, `png`,
                                                # `jpg`, `jpeg`, `gif`, `webp`, `avif`, and
                                                # `mp4`, `webm`, `mov`, `m4v` for clips
  "docs/*.png",                                 #   a path or glob in your repository
  "https://cdn.example.com/after.webp",         #   or a file hosted anywhere
]
Left out Falls back to
example_workflows workflows/, workflow/, examples/, example/, example_workflows/
docs, funding [project.urls]
An installed pack's fields The copy on disk, then the repository

Workflow thumbnails are not declared. An image beside a workflow and named for it is paired with it automatically, following ComfyUI's workflow templates convention: workflows/hdr.json picks up workflows/hdr.webp, .png, .jpg, .jpeg or .gif, and a numbered variant such as hdr-1.png counts too. Workflows without one show as a plain row.

Optional requirements

Optional dependencies need no field. Open Manager reads them from the files Python projects already use and offers each group once your pack installs, one at a time or all together, and again from the Optional tab on your page. Choosing groups shows what they would change before anything installs, as a pack install does, and they install under the same rules as requirements.txt: the install policy, the packages held back to protect ComfyUI, and the user's substitutions. When an update leaves a group the user chose short, it is offered again, ticked. requirements.txt stays the base install.

Declared as Group name
requirements/<group>.txt The file name
requirements-<group>.txt or requirements_<group>.txt beside requirements.txt The part after requirements
[project.optional-dependencies] in pyproject.toml The extra
Description The first paragraph of the comment a file opens with, or the comment beside an extra's name
Package notes A comment after a package, as pip reads one
-r lines in a group Followed while they stay inside your pack
A file and an extra of one name The file is the group, and takes the extra's comment when it opens with none
Not offered Files requirements.txt includes, files another group includes, dev, test, docs, lint and the like, and base, common, core and the like
Aggregates A file of only -r lines, or a group made only of others, as all often is, is not offered: All covers it
[project.optional-dependencies]
llm = ["llama-index-core>=0.14", "httpx"]   # the LLM nodes
pdf = ["xhtml2pdf"]                         # .pdf on Save DOC
all = ["my-pack[llm,pdf]"]                  # covered by All, not offered
# requirements/llm.txt
# The LLM nodes, on llama-index.
llama-index-core>=0.14   # documents, indexes and chat
httpx                    # the web tools agents call

Capabilities

Your own account of what your pack does, in fixed words so that two packs describe themselves the same way.

filesystem network subprocess binaries environment dynamic_code packages models credentials telemetry compilation hardware

Outside the list Refused, and named on your page as unrecognised
Case and hyphens Forgiven. Dynamic-Code resolves to dynamic_code
Declaring nothing No panel
Not a substitute for The archive inspection, which reads what is actually in the box

Themes

A ComfyUI colour palette plus an optional extras block: gradient or flat headers per node category or class, a title icon, an image behind node bodies, see-through bodies, a graph backdrop, shadow colours, a selection glow and a link style. For OM Nodes, tokens, named parts and scoped CSS restyle every part of a node. Packs ship them, users add them from the pack page.

[tool.open_manager]
themes = ["themes/my-theme/my-theme.json"]

Full reference in docs/THEMES.md. Examples in open_manager/themes/.


Licence

MIT, see LICENSE.

The GitHub mark shown on links to github.com is mark-github from Octicons, MIT licensed, Copyright (c) GitHub Inc. It is used only for links that go to GitHub.

Metadata

Release files for comfyui-open-manager 0.7.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for comfyui-open-manager 0.7.1
File Size Uploaded Provenance Actions
comfyui_open_manager-0.7.1.tar.gz 1.6 MB With provenance Details for comfyui_open_manager-0.7.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for comfyui-open-manager 0.7.1
File Interpreter ABI Platform Actions
comfyui_open_manager-0.7.1-py3-none-any.whl Python 3 none any Details for comfyui_open_manager-0.7.1-py3-none-any.whl

Total release size: 3.4 MB

Release files / comfyui_open_manager-0.7.1.tar.gz

Download URL comfyui_open_manager-0.7.1.tar.gz
Size 1.6 MB
Tags Source
SHA-256 checksum
How to use checksums
d682cdb3d3a21357ece8afa5637076fab98d0a3165b14af4d707b55a139c5e5b
BLAKE2b-256 checksum
How to use checksums
ceada3f46e205882764dd6b52b56493fad4e29f1098aa8560aea6afa5e396bc4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.

Transparency log

Release files / comfyui_open_manager-0.7.1-py3-none-any.whl

Download URL comfyui_open_manager-0.7.1-py3-none-any.whl
Size 1.7 MB
Tags Python 3
SHA-256 checksum
How to use checksums
1f816e79cddaefa4360046e772aa2d94ec56c0c7cdf5bfd18b44cea30e96c5ae
BLAKE2b-256 checksum
How to use checksums
15155a69dcb9e012ba05f461953f5f0225ba2e38a0081392bbc95e2a56a38dd4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.

Transparency log

Security for comfyui-open-manager 0.7.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for comfyui_open_manager-0.7.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.7.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page