report-bug

# Self-heal & report bugs (make the ecosystem better) Goal: when something is broken, don't just stop — **diagnose it, try to fix it so the user keeps working, and get the fix/report to whoever can fix it upstream.** **Scope of autonomy — read this first.** For defects in **OUR repos** (`artokun/comfyui-mcp`, `comfyui-mcp-panel`, `comfyui-mcp-issue-worker`) act **autonomously**: fix-then-file, then **inform** the user with a short summary — don't pepper them with permission prompts. For **THIRD-PARTY / ComfyUI-core** defects it is **offer-and-ask** (Step 6): you propose the workaround and/or the report and act only once the user agrees — it's their call to patch someone else's node or post to someone else's tracker. (Even for our repos, DO pause for: a fix that touches the user's own workflow/data, anything large/risky, or anything you can't make safe — explain and ask.) This is for **bugs in software**, not ordinary workflow/generation errors (OOM, missing model, bad params → use `troubleshooting`). First decide whose bug it is. ## When to file — bias HARD toward reporting (we're in beta) While comfyui-mcp is in beta, **the default is to file.** You do NOT need to be blocked, and it does NOT need to be fatal. If you notice a defect in our software, report it — even after you've already recovered. File when any of these happen: - A tool/panel/orchestrator call **errors**, throws, or crashes ComfyUI. - A tool returns **wrong, misleading, empty, or malformed** output — or...