comfyui-mcp 0.50.18 → 0.50.20

package/dist/orchestrator/panel-tools.js

@@ -5349,11 +5349,45 @@ export function buildPanelToolDefs() {
                 text: (p) => fixedCapHint("selected node(s)", replyCount(p, "nodes"), p.selected_count, "Ask the user to select fewer nodes, or read the ones you need by id with panel_query_graph {ids:[…], fields:'detail'}, which DOES take limit and max_chars."),
             },
         ])),
-        def("panel_view_nodes_in_viewport", "ONLY the nodes inside the current VIEWPORT (pan+zoom) — a screen-region subset, NOT the whole open graph (that is panel_graph_outline, which is what 'show me what's on the canvas' means). Use this to SCOPE your work to what's on their screen: when they say \"these nodes\", \"the ones here\", \"what am I looking at right now\", or when a graph is large and you only need the region in front of them. Returns the viewport rect in graph coordinates (x, y, width, height, zoom), `node_count` (whole graph) vs `in_view_count`, and the detail summary of each visible node. A node counts as visible if any part of it overlaps the viewport. On a big canvas this is dramatically cheaper than reading everything. Read-only.", {}, async (_args, ctx) => withTruncationHints(await ctx.call({ cmd: "graph_view_nodes_in_viewport" }), [
+        def("panel_view_nodes_in_viewport", "ONLY the nodes inside the current VIEWPORT (pan+zoom) — a screen-region subset, NOT the whole open graph (that is panel_graph_outline, which is what 'show me what's on the canvas' means). Use this to SCOPE your work to what's on their screen: when they say \"these nodes\", \"the ones here\", \"what am I looking at right now\", or when a graph is large and you only need the region in front of them. Returns the viewport rect in graph coordinates (x, y, width, height, zoom), `node_count` (whole graph) vs `in_view_count`, and the detail summary of each visible node. A node counts as visible if any part of it overlaps the viewport. On a big canvas this is dramatically cheaper than reading everything. This tool does NOT filter to specific nodes — to read one node's exact slot/widget detail use panel_query_graph {ids:[…], fields:'detail'}. Read-only.", {
+            // #845/#754 — the panel has enforced a CHARACTER budget here since the
+            // 135k-character reply that motivated it, but the budget was unreachable:
+            // this schema was `{}` and the call below passed no arguments, so the
+            // default applied and no caller could raise or lower it. Its sibling
+            // panel_query_graph has always exposed the lever. An enforced-but-hidden
+            // knob is the worst of both — callers hit a cap they cannot see or move.
+            //
+            // The range described here is the PANEL's own clamp (viewport-char-bound.js),
+            // not panel_graph_outline's 500–60000. Two different clamps already exist;
+            // describing the one that is not enforced would make this text false, and a
+            // schema that lies about its bounds is worse than one that omits them.
+            max_chars: z
+                .number()
+                .int()
+                .positive()
+                // Declared so the #809 gate can check the ceiling this tool STATES
+                // against the one it enforces. Only the ceiling: the floor stays
+                // undeclared so a small value clamps up panel-side rather than being
+                // refused — a caller asking for 1000 wants less, not an error.
+                .max(200000)
+                .optional()
+                .describe("Character budget for the whole reply (default 24000, clamped 2000–200000). Nodes are taken in view order until it is spent, never partially serialized. `in_view_count` keeps describing the SCREEN, so compare it to nodes.length to see what was withheld."),
+        }, async (args, ctx) => withTruncationHints(await ctx.call({
+            cmd: "graph_view_nodes_in_viewport",
+            // Forwarded only when supplied: an explicit `undefined` on the wire
+            // would reach the panel's normalizer as a nonsense value, and it
+            // deliberately falls back to the default rather than to zero — but
+            // sending it at all would misreport this caller as having asked.
+            ...(args.max_chars === undefined ? {} : { max_chars: args.max_chars }),
+        }), [
             {
                 flag: "truncated",
                 key: "truncation_hint",
-                text: (p) => fixedCapHint("visible node(s)", replyCount(p, "nodes"), p.in_view_count, "Ask the user to zoom in so fewer nodes are on screen, or read the region with panel_query_graph (which DOES take limit and max_chars) / panel_graph_outline for the whole graph."),
+                text: (p) => fixedCapHint("visible node(s)", replyCount(p, "nodes"), p.in_view_count, 
+                // #754 — this remedy used to send the caller to panel_query_graph
+                // "which DOES take limit and max_chars", because this tool did not.
+                // It does now, so the first move is the lever in your own hand.
+                "Raise `max_chars` up to 200000 to see more of the same screen, or ask the user to zoom in so fewer nodes are on it. To read SPECIFIC nodes instead, panel_query_graph {ids:[…], fields:'detail'}; for the whole graph, panel_graph_outline."),
             },
         ])),
         def("panel_audit_prompt_director", "Audit Prompt Director on the LIVE canvas without changing it. Correlates Prompt Director/Producer/Auto/Context/Reference/Critic widget values and wiring with detected model-loader filenames, every LoRA loader's actual model/CLIP strengths, and Prompt Director's latest sanitized runtime edit plan, resolved Model Explorer metadata, warnings, exact final prompt, and critic verdict. Returns observations plus proposed panel_set_widget changes with requires_confirmation=true. Call this when Prompt Director nodes are present, before saying the model/LoRA setup is correct, or when an edit prompt is ignored. READ-ONLY: present useful findings to the user and ask before applying any recommendation unless they already explicitly asked you to fix it.", {}, async (_args, ctx) => ctx.call({ cmd: "graph_prompt_director_audit" })),
@@ -5972,6 +6006,20 @@ export function buildPanelToolDefs() {
                 isRetryableRunToNodeStampRace(res, rejection)) {
                 scopeRebuilt = true;
                 try {
+                    // #1050 — SETTLE before re-issuing. The panel refuses this race when the
+                    // graph changed between dispatch and apply, and re-dispatching in the
+                    // same tick lands in the SAME window: a reporter's retry raced
+                    // identically and instantly, so the one re-issue was spent for nothing
+                    // and the run was refused twice with nothing queued.
+                    //
+                    // This is a SETTLE PAUSE, not the mutation-quiescence barrier the report
+                    // asked for. The panel exposes no such signal, and inventing a
+                    // graph-is-quiet reading from out here would be guessing at the
+                    // frontend's state. It buys pending edits a moment to land — exactly
+                    // what the reconnect retry already does for a dropped socket — and
+                    // nothing more. A graph still moving after it (a user actively editing)
+                    // races again and is SURFACED, never re-raced.
+                    await sleep(retrySettleMs());
                     res = await ctx.call(runCmd, 20000);
                     rejection = detectRunRejection(res);
                 }
@@ -5999,9 +6047,11 @@ export function buildPanelToolDefs() {
                     return rejection;
                 return appendToolResultText(rejection, `\n\n(Dispatch history: the first graph_run was refused by the panel's run-to-node ` +
                     `graph-stamp race, which CERTIFIED that nothing was queued, so the scoped run was ` +
-                    `re-issued exactly once. The failure above is that SECOND dispatch; it was not ` +
-                    `retried again. Judge whether anything was queued from that message alone — the ` +
-                    `first dispatch definitely queued nothing.)`);
+                    `re-issued exactly once — after a short pause to let pending graph edits land ` +
+                    `(#1050). The failure above is that SECOND dispatch; it was not retried again. ` +
+                    `Judge whether anything was queued from that message alone — the first dispatch ` +
+                    `definitely queued nothing. Racing AGAIN after the pause means the graph is still ` +
+                    `changing under the run: let the canvas settle, then re-run.)`);
             }
             // Attribute this genuine queue to ourselves so a later panel_run in the
             // same batch recognizes the in-flight job as our own and doesn't false-warn