claude mcp add <name> -- <command>.mcpServers in the MCP config file.npx degit artokun/comfyui-mcp/plugin/skills/report-bug#main ~/.claude/skills/report-bugFor one project only, change the path to .claude/skills/report-bug.
This one runs on your machine and can reach your files. Read the README below before you connect it.
Paste into Claude, ChatGPT or Cursor.
comfyui-mcp and the ComfyUI Agent Panel are no longer maintained. Their GitHub issue
trackers are closed and the AI-triage intake Worker is gone, so there is nowhere for a
report to go. report_issue still exists so older prompts get a clear answer, but it
files nothing and contacts nothing.
When the user hits a defect in comfyui-mcp or the panel:
Do NOT:
report_issue expecting it to file (it returns the archived notice);Unchanged: these go to the node or project's own GitHub, and it is offer-and-ask — you
propose the workaround and/or the report, and act only once the user agrees.
troubleshooting still covers ordinary generation failures (OOM, a missing model,
bad params).
| 1 | |
| 2 | name report-bug |
| 3 | description ARCHIVED. comfyui-mcp is no longer maintained and its issue trackers are closed - do NOT file, and do not use report_issue to try. When the user hits a defect in comfyui-mcp or the sidebar panel, say plainly that this project is archived and point them at ComfyUI's official agent and MCP tooling (Comfy Agent / Comfy MCP by Comfy-Org; https://docs.comfy.org/agent-tools). For third-party custom-node or ComfyUI-core bugs, offer their own GitHub as before, and only with the user's go-ahead. Triggers on "report this", "fix this bug", or any error in our software - the answer is the same. |
| 4 | |
| 5 | |
| 6 | # This project is archived — do not file issues |
| 7 | |
| 8 | comfyui-mcp and the ComfyUI Agent Panel are no longer maintained. Their GitHub issue |
| 9 | trackers are closed and the AI-triage intake Worker is gone, so there is nowhere for a |
| 10 | report to go. `report_issue` still exists so older prompts get a clear answer, but it |
| 11 | files nothing and contacts nothing. |
| 12 | |
| 13 | ## What to do instead |
| 14 | |
| 15 | When the user hits a defect in comfyui-mcp or the panel: |
| 16 | |
| 17 | Say plainly that this project is archived and will not receive fixes. |
| 18 | Point them at ComfyUI's **official** agent and MCP tooling, built and supported by |
| 19 | the Comfy-Org team: |
| 20 | Comfy Agent: https://comfy.org/agent |
| 21 | Agent tools documentation: https://docs.comfy.org/agent-tools |
| 22 | Comfy MCP: https://comfy.org/mcp/ |
| 23 | Source: https://github.com/Comfy-Org/comfy-mcp |
| 24 | If the task can still be completed with what works here, complete it; if not, say |
| 25 | which official tool covers it. |
| 26 | |
| 27 | Do NOT: |
| 28 | call `report_issue` expecting it to file (it returns the archived notice); |
| 29 | draft an issue body, look for a duplicate, or suggest the user open one by hand — |
| 30 | the trackers reject new issues; |
| 31 | spend turns on a fix-then-file loop for our repos; there is no "file". |
| 32 | |
| 33 | ## Third-party and ComfyUI-core bugs |
| 34 | |
| 35 | Unchanged: these go to the node or project's own GitHub, and it is offer-and-ask — you |
| 36 | propose the workaround and/or the report, and act only once the user agrees. |
| 37 | `troubleshooting` still covers ordinary generation failures (OOM, a missing model, |
| 38 | bad params). |
| 39 | |
| 40 | ## Absolute rules |
| 41 | |
| 42 | Scrub secrets before anything leaves the machine, every time. |
| 43 | Never claim a fix you did not verify. |
| 44 | Never touch the user's workflow data without asking. |
| 45 | |
| 46 | ## Sources |
| 47 | |
| 48 | **Official:** ComfyUI agent tools documentation (https://docs.comfy.org/agent-tools) and Comfy MCP (https://comfy.org/mcp/). |
| 49 | **Empirical:** none. Archive policy, not reverse-engineered from a vendor graph. |
| 50 |
Follow-up confirms the #2854 `panel_run` dispatch failure no longer reproduces after upgrading comfyui-mcp-panel from 0.15.162 to 0.15.173 and restarting ComfyUI; the first run on the unchanged workflow queued successfully. comfyui-mcp remained at 0.52.190. The session had also observed an explicit stale-bundle refusal, and the floor-only status verdict did not surface the available panel update prominently.
**Diagnosed and fixed — but the fix is in the other repository, so nothing here will close automatically.** Fix: **artokun/comfyui-mcp-panel#2248** (green, `[check-panel-scope] OK`, 8355 unit tests pass). **Correcting the report's premise, which was reasonable but wrong.** The string is composed, not literal — `refuseUnstableRunDispatch` joins a `changed[]` array, so `"backend socket down"` is an element and the sentence reads "backend socket down changed while…". That is why grepping the installed package and the panel pack found nothing. The emitter is `web/js/comfyui-mcp-panel.js`, in the p… read the rest
**Do not close this on the "no longer reproduces" follow-up. The upgrade did not fix it — the restart did, and only until the flag arms again.** That report says the failure stopped after upgrading comfyui-mcp-panel 0.15.162 → 0.15.173 **and restarting ComfyUI**. This defect is a *sticky flag*, and a restart clears it: Every session starts with it false. So a restart guarantees the first run dispatches, whatever version is installed — the observation is fully explained without the upgrade doing anything. **And the defect is still in the code they upgraded to.** Checked against panel `origin/ma… read the rest
Duplicate report with current-version confirmation: on macOS (darwin 25.6.0), ComfyUI 0.18.1, comfyui-mcp 0.52.199 and panel 0.15.179, `panel_run` was refused 10+ times over ~1.5 hours with the same `backend socket down changed while the run was preparing to dispatch` error. `panel_graph_outline` simultaneously reported `backend_socket: "up"`, `mutations_ready: true`, and `canvas_binding: "bound"`; widget/connect/disconnect calls and user-initiated Queue Prompt runs succeeded. A soft `panel_reload` did not change the failure. Both reported packages are current releases.