comfyui-mcp 0.50.28 → 0.50.30

package/dist/orchestrator/panel-tools.js

@@ -5573,7 +5573,7 @@ export function buildPanelToolDefs() {
                 },
             },
         ])),
-        def("panel_add_node", "Add a node to the user's OPEN ComfyUI graph by class_type (e.g. 'KSampler', 'CheckpointLoaderSimple'). The user sees it appear live; Ctrl+Z undoes it. Returns the created node's id, slots, and default widget values. Frontend-only virtual types are addable too: 'Note' and 'MarkdownNote' — the supported way to ANNOTATE a workflow with on-canvas instructions (add the node, then put the text in its 'text' widget via panel_set_widget) — plus 'Reroute' and 'PrimitiveNode'. These are LiteGraph-native and never appear in the backend node registry, so they legitimately bypass the backend class_type check.", {
+        def("panel_add_node", "Add a node to the user's OPEN ComfyUI graph by class_type (e.g. 'KSampler', 'CheckpointLoaderSimple'). The user sees it appear live; Ctrl+Z undoes it. Returns the created node's id, slots, and default widget values. Frontend-only virtual types are addable too: 'Note' and 'MarkdownNote' — the supported way to ANNOTATE a workflow with on-canvas instructions (add the node, then put the text in its 'text' widget via panel_set_widget) — plus 'Reroute' and 'PrimitiveNode'. These are LiteGraph-native and never appear in the backend node registry, so they legitimately bypass the backend class_type check. ADD NODES ONE AT A TIME, not as a parallel batch: each add carries a fresh /object_info payload and those register SERIALLY, so N concurrent adds become N sequential refresh cycles. On a large install that outruns the 30s per-command deadline and the later adds time out WHILE STILL QUEUED — they then apply when their turn arrives, leaving nodes you were told had failed (panel#767). Sequential adds each get the refresh to themselves and stay well inside the deadline.", {
             class_type: z.string().describe("Exact ComfyUI node class_type to create."),
             pos: xy()
                 .optional()
@@ -7769,7 +7769,23 @@ export function buildPanelToolDefs() {
                         "INSTEAD: unlike this panel-scoped restart, it is not tied to a browser tab " +
                         "— it acts on the ComfyUI this server is configured for, which it CAN " +
                         "identify and check before stopping. Or restart ComfyUI from whatever " +
-                        "launches it (its own launcher, the Desktop app, or your terminal).",
+                        "launches it (its own launcher, the Desktop app, or your terminal)." +
+                        // artokun/comfyui-mcp-panel#769 — a REMOTE ComfyUI reached over a
+                        // tunnel or port-forward has a LOOPBACK host, and remoteUrlActive is
+                        // derived from exactly that (`forceRemote || !isLoopbackHost(host)`).
+                        // So a cloud pod fronted at 127.0.0.1:<port> classifies as LOCAL, this
+                        // branch runs, and it correctly reports it cannot find a local process
+                        // to account for — because there isn't one. The refusal is right about
+                        // what it observed and useless about what to do, since the reader is
+                        // looking for a local install that does not exist. Name the one setting
+                        // that re-classifies it; it is a config fix, not a workaround.
+                        " NOTE: if this ComfyUI is actually REMOTE but reached through a tunnel " +
+                        "or port-forward (a 127.0.0.1 address that is not this machine), it is " +
+                        "being classified as local because that classification reads the HOST — " +
+                        "which proves the route is local, not the instance. Set " +
+                        "COMFYUI_MCP_FORCE_REMOTE=1 (or pass --force-remote) and this tool takes " +
+                        "the remote path, which restarts through ComfyUI-Manager and does not " +
+                        "need a local process to account for.",
                 });
             }
             if (preflightBound) {
@@ -7999,6 +8015,38 @@ export function buildPanelToolDefs() {
                 // 3.x — #425, panel #253/#266) AND the target is a LOCAL, process-controllable
                 // ComfyUI, fall back to the headless managed restart (kill + relaunch). A
                 // busy-guard / security refusal is NOT eligible (rebootNoEndpoint excludes them).
+                // #425 RECURRENCE (remote RunPod, 0.50.27). The managed fallback below is
+                // LOCAL-ONLY and correctly does nothing here — there is no process on this
+                // machine to restart. But falling through returned the bare "no reboot
+                // endpoint … was NOT restarted", which is where the owner's report ended:
+                // freshly installed custom nodes stayed unavailable "until a provider/host
+                // restart", and nothing had told them a host restart was the requirement.
+                //
+                // Say what this target actually needs. We do NOT cycle the pod ourselves:
+                // stop/resume bills, interrupts everything else on the box, and on a spot
+                // instance may not come back — that is the user's call, not a side effect
+                // of asking to restart ComfyUI.
+                if (isRemoteMode() && rebootNoEndpoint(res)) {
+                    return ok({
+                        rebooting: false,
+                        ready: false,
+                        confirmed_cycle: false,
+                        note: `${toolResultText(res)}\n\n` +
+                            `This ComfyUI is REMOTE, so the managed restart that covers a local install ` +
+                            `does not apply — there is no process on this machine to cycle. A 405 from a ` +
+                            `Manager reboot route means that route is not registered on the running ` +
+                            `Manager (the frontend catchall answers every unregistered POST with 405), so ` +
+                            `it is a Manager version/dialect that exposes no reboot API rather than an ` +
+                            `auth failure.\n\n` +
+                            `WHAT WILL WORK: restart the HOST. Anything you just installed — custom nodes ` +
+                            `especially — stays unavailable until the ComfyUI process itself restarts, and ` +
+                            `nothing this MCP can reach will load it. On RunPod, runpod (action:"stop") ` +
+                            `then runpod (action:"start") with the pod_id cycles the box (stop ends ` +
+                            `billing; start bills again). Otherwise restart the container or provider ` +
+                            `however you normally would.\n\n` +
+                            `Do NOT report the newly installed nodes as ready: they are not loaded.`,
+                    });
+                }
                 if (!isRemoteMode() &&
                     rebootNoEndpoint(res) &&
                     // ENDPOINT BINDING: restartComfyUI() acts on the orchestrator's GLOBAL config