panel-node-pack-sync

Synchronizes the ComfyUI sidebar panel node-pack version with the installed comfyui-mcp orchestrator.

715|111|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/artokun/comfyui-mcp --skill panel-node-pack-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: panel-node-pack-sync
Source: https://github.com/artokun/comfyui-mcp/tree/main/plugin/skills/panel-node-pack-sync
Command: npx skills add https://github.com/artokun/comfyui-mcp --skill panel-node-pack-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The comfyui-mcp orchestrator and the comfyui-agent-panel sidebar ship separately, so updating one leaves the other behind and causes confusing version-drift failures like unimplemented bridge commands or missing sidebar features. This Skill detects that drift, syncs the panel through a verified install path, and reports only the version re-read from disk.

Core Features & Use Cases

  • Version Drift Detection: Reads the installed panel version against the orchestrator's required floor via install_comfyui(action:'panel', panel_action:'status') and acts on the returned sync.decision.
  • Verified Sync: Runs install_comfyui(action:'panel', panel_action:'sync'), reports the verifiedVersion re-read from disk, and states that a ComfyUI restart is required.
  • Pin Respect: Warns instead of syncing when the user pinned the panel, offers an explicit unpin flow, and handles env-based pins that cannot be cleared programmatically.
  • Use Case: After running npm i -g comfyui-mcp, a sidebar graph command fails with "panel is too old"; the Skill checks status, syncs the panel, and reports the verified on-disk version.

Quick Start

Check whether my ComfyUI agent panel version matches my comfyui-mcp orchestrator and sync it if it is behind.

Frequently Asked Questions about panel-node-pack-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update the ComfyUI agent panel after updating comfyui-mcp?

Run install_comfyui with action 'panel' and panel_action 'status' to check drift, then panel_action 'sync' to update through the verified path. ComfyUI must be restarted afterwards to load the new panel version.

Why does a ComfyUI sidebar command fail after an orchestrator update?

The orchestrator and panel ship separately, so a new orchestrator may call bridge commands an old panel does not implement. Check the panel status decision and sync the panel to the required version.

Can I pin the ComfyUI panel to a specific version?

Yes, use install_comfyui panel_action 'pin' with the currently installed version and a reason. While pinned, all update paths refuse to move the panel until you explicitly unpin.

What happens if the panel pin is set via environment variable?

An env-based pin from COMFYUI_MCP_PANEL_PIN cannot be cleared by the unpin action. You must unset it in your environment or ~/.comfyui-mcp/.env and restart the orchestrator yourself.

Why does the panel version not change after a sync?

A shadow copy like a .bak directory in custom_nodes can override the real panel in the browser, or ComfyUI-Manager may report a drained queue without installing anything. Move shadow copies out of custom_nodes and re-check the status.