Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions development/comfyui-server/startup-flags.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -173,6 +173,8 @@ python main.py --disable-auto-launch

## VRAM & Memory

On Nvidia GPUs, `--async-offload` and `--enable-dynamic-vram` are enabled by default. See the table below for platform-specific defaults.

<Note>
VRAM mode flags (`--gpu-only`, `--highvram`, `--lowvram`, `--novram`, `--cpu`) are mutually exclusive.
</Note>
Expand Down
31 changes: 31 additions & 0 deletions installation/update_comfyui.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -131,6 +131,37 @@ git checkout master
</Tab>
</Tabs>

## How to Update ComfyUI Manager

ComfyUI Manager is a custom node that provides installation and management of other custom nodes, models, and snapshots. It is separate from the ComfyUI core code and has its own update process.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Clarify that Manager’s update model depends on the installation type.

Line 136 says Manager is separate from ComfyUI core and has its own update process, but the Portable section says it is bundled into core and updated with ComfyUI. Make the opening description explicitly scope the separate custom-node workflow to manual installations. Otherwise the docs tell a split-brain update story.

Suggested wording
-ComfyUI Manager is a custom node that provides installation and management of other custom nodes, models, and snapshots. It is separate from the ComfyUI core code and has its own update process.
+ComfyUI Manager provides installation and management of other custom nodes, models, and snapshots. Its update process depends on the installation type: manual installations manage it separately, while Windows Portable bundles it into ComfyUI core.

Also applies to: 159-160

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@installation/update_comfyui.mdx` at line 136, Update the opening ComfyUI
Manager description in the installation documentation to state that its separate
custom-node update workflow applies to manual installations, while Portable
installations bundle Manager with ComfyUI and update it through the core
process. Ensure the corresponding wording at the additionally affected Manager
description remains consistent.


<AccordionGroup>
<Accordion title="Update via Manager UI (recommended)">
The simplest way to update Manager is through its own interface:

1. Open the **ComfyUI Manager** dialog by clicking the **Manager** button in the ComfyUI toolbar
2. Go to the **Custom Nodes** tab (New UI) or the node list (Legacy UI)
3. Find **ComfyUI-Manager** in the list and click the **Update** or **Install/Update** button
4. Restart ComfyUI after the update completes
</Accordion>

<Accordion title="Update via Git (manual installation)">
If you installed ComfyUI Manager manually via Git, update it with:

```bash
cd custom_nodes/ComfyUI-Manager
git pull
```

Then restart ComfyUI.
</Accordion>

<Accordion title="Portable version">
For the Windows Portable version, ComfyUI Manager is built into the core. Update it by updating ComfyUI itself using one of the update scripts in the `update/` folder, or through the Manager UI as described above.
</Accordion>
</AccordionGroup>

<Note>If the Manager is missing or disabled after an update, re-enable it via `--enable-manager` launch flag. See the [ComfyUI Manager Overview](/manager/overview) for details.</Note>

## ComfyUI Version Types

Expand Down
Loading