panel-node-pack-sync

Featured

Keep the ComfyUI sidebar panel node-pack (comfyui-agent-panel) in step with the orchestrator after comfyui-mcp updates. Use this whenever the orchestrator was just updated (install_comfyui (action:"self_update"), npm i -g comfyui-mcp, a new version in the ENVIRONMENT line), when a panel/bridge command fails in a way that smells like version drift ("panel is too old", a graph_/ui_ command the panel doesn't implement, a feature that works in the docs but not in the sidebar), or when the user asks to update/pin/unpin the panel. It checks the installed panel version against what THIS orchestrator build needs, RESPECTS an explicit version pin (warn-only, never move a pinned user), offers a clear way to unset the pin, runs the sync through the verified install_comfyui(action:'panel') path, and reports the version RE-READ from disk. Never claim a sync that did not happen.

AI & Automation 763 stars 131 forks Updated 5 days ago MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Keep the panel node-pack in sync with the orchestrator The orchestrator (`comfyui-mcp`, from npm) and the sidebar panel (`comfyui-agent-panel` on the Comfy Registry, repo `comfyui-mcp-panel`) ship **separately**. Updating one does not update the other. A new orchestrator driving an old panel fails in confusing ways, such as a bridge command the panel doesn't implement or a feature that exists in the docs but not in the sidebar, and those failures are hard for a user to diagnose. This skill closes that gap. ## The two rules that outrank everything else here 1. **Never report a sync that did not happen.** This whole feature sits on top of the fabricate-success fixes (#639/#641): ComfyUI-Manager reports its queue "drained" even when it never enqueued anything, and a `.bak`-style copy in `custom_nodes` can shadow the real panel in the browser. So the only version you may ever tell the user is the one **read back from disk after the fact**. If the tool throws, the sync FAILED. Say so plainly. Do not soften it, do not retry it into a success, do not report the version you *intended* to install. 2. **Never move a pinned user.** A pin is a promise. If the user pinned the panel, you **warn and stop**. You do not unpin for them, you do not "just this once", you do not sync anyway because the new version is obviously better. Offer to clear the pin, and act only if they say yes. ## Step 1 — Look before you touch anything ``` install_comfyui(action:'pane...

Details

Author: artokun
Repository: artokun/comfyui-mcp
Created: 7 months ago
Last Updated: 5 days ago
Language: TypeScript
License: MIT

Integrates with

OpenAI · AI Ollama · AI Model Context Protocol · AI

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

monorepo-deps

End-to-end syncpack + manypkg flow for an npm monorepo: check, fix, update, and maintain `.syncpackrc.json`. Trigger on /monorepo-deps, "update deps", "sync deps", "check deps", "fix syncpackrc", "create syncpackrc", or "my lock file is out of sync". Use syncpack-usage / syncpack-cli / syncpack-config for syncpack API and config details, manypkg-usage for manypkg specifics — this skill orchestrates them.

14 Updated 2 weeks ago

allemaar

AI & Automation Featured

panel-operations

On-demand procedures for the ComfyUI sidebar panel agent that are too long to sit in the system prompt. Read it when a task lands in one of these areas. subgraph boundary rails and blueprint reuse, merging or composing workflows across tabs, pinning your edits to one workflow, opening staged or downloaded workflow files, untangling Get/Set-bus and rgthree toggle-heavy graphs, authoring rgthree Fast Groups nodes, the LoRA Manager autocomplete-node limitation, the CivitAI browser flow, downloading model weights, reading hardware and runtime stats, Prompt Director audits, custom-node crash recovery, run-to-node render debugging, and multi-stage pipeline chaining. Each section is a lookup, not background reading. Reach for the one you need instead of guessing, and follow the tool's own description for parameter detail.

763 Updated 5 days ago

artokun

AI & Automation Listed

agent-sync

Manage the user's agent-sync setup - check what is deployed where, sync devices, resolve drift, change routing, adopt existing config, or diagnose why a skill or MCP server is missing from an agent. Use when the user says sync my skills, what is deployed, why does Cursor not have X, my skills are out of date, adopt what is on this machine, or asks to route an artifact to particular agents.

2 Updated 4 days ago

Alpha-30-creator