comfyui-mcp/dist/orchestrator/pair-durability.js

Local-first, agent-native control plane for ComfyUI — MCP server + autonomous sidebar agent that drives your live graph in natural language on ANY LLM: Claude/ChatGPT/Gemini on your subscription (no API key), free local models via Ollama (fully offline),

/**
 * #875 — will this pairing URL still work after the orchestrator restarts?
 *
 * A user asked to pin the orchestrator version because "updating the npm version
 * bricks my communication with the agent". The version is not the cause. The
 * self-restarter is on by default, checks npm hourly, and restarts into new code
 * whenever the agent is idle — and a restart rotates up to two independent parts
 * of the URL the phone saved:
 *
 *   1. THE TOKEN. Generated per session unless COMFYUI_MCP_PAIR_TOKEN is pinned.
 *   2. THE HOSTNAME, tunnel mode only. Phone pairing opens a cloudflared QUICK
 *      tunnel, which mints a fresh random `<rand>.trycloudflare.com` every run.
 *
 * So a default-on feature silently invalidates another default-on feature, and
 * nothing at pair time says so. The user is left to infer it from a phone that
 * stopped working, which is how this arrived as "pin the version" rather than as
 * "my pairing URL expired".
 *
 * IMPORTANT, and the reason this file states the tunnel case unconditionally:
 * COMFYUI_MCP_TUNNEL_BACKEND=relay does NOT give a stable phone-pairing URL. That
 * setting is read only by services/secure-bridge.ts, for the `connect` path's
 * remote-pod bridge. The pairing path calls startQuickTunnel() directly and never
 * consults it. A relay operator therefore gets exactly the same rotating
 * trycloudflare hostname as everyone else, and advice to "deploy a relay" would
 * send them to build a Cloudflare Worker that cannot fix this. Whoever changes
 * pairing to honour a backend selection must revisit `hostRotates` here.
 *
 * This module only DESCRIBES. It does not defer restarts or persist a token —
 * both change behaviour the user did not ask for (persisting a
 * password-equivalent token removes the auto-expiry that a per-run token gives
 * you today), and neither is mine to decide silently.
 */
/**
 * Describe the URL's durability from configuration alone — no probing, no
 * guessing. Every branch below is a fact about how the URL was constructed.
 */
export function pairUrlDurability(input) {
    const rotates = [];
    // Tunnel pairing is ALWAYS a quick tunnel (see the note above): the hostname
    // is regenerated per run with no way to pin it.
    if (input.mode === "tunnel")
        rotates.push("hostname");
    if (!input.stableToken)
        rotates.push("token");
    if (rotates.length === 0) {
        return {
            survivesRestart: true,
            rotates: [],
            note: "This URL survives an orchestrator restart: the pairing token is stable (persisted, or " +
                "pinned via COMFYUI_MCP_PAIR_TOKEN) and the LAN address does not change per run. (If your router reassigns this machine a different " +
                "IP, the address changes for that reason, not because of a restart.)",
        };
    }
    // Name the parts, then the cause, then the remedy that exists for each. The
    // restarter clause is stated only when it is actually armed.
    const what = rotates.length === 2
        ? "both its hostname and its token are regenerated"
        : rotates[0] === "hostname"
            ? "its hostname is regenerated"
            : "its token is regenerated";
    const cause = input.autoRestart
        ? "The orchestrator restarts on its own to apply updates (hourly check, when idle), so this " +
            "can happen without you doing anything."
        : "Automatic restarts are disabled here, so this only happens when the orchestrator is " +
            "restarted deliberately.";
    const remedy = rotates.includes("hostname")
        ? "There is no way to pin the tunnel hostname today — phone pairing always uses a cloudflared " +
            "quick tunnel, and COMFYUI_MCP_TUNNEL_BACKEND=relay does not apply to it. To keep a link " +
            "that survives restarts, pair over LAN (the token is persisted, so a LAN URL keeps " +
            "working); otherwise re-pair from the panel after a restart. " +
            // #1963 — CHECK still runs (and the panel is told); APPLY does not, because
            // a restart mints a new hostname. Sticky on the pairing itself, not the
            // live socket: a locked screen is still paired. The pair-time toggle
            // (default ON) and Update now are how a desk session moves forward.
            "While this tunnel pairing is active, automatic updates are CHECK-ONLY — they will not " +
            "restart and disconnect this device. They apply when you are back at the desk, when you " +
            "turn off “Don't update while my phone is paired”, or when you choose Update now." +
            (rotates.includes("token")
                ? " (Pinning COMFYUI_MCP_PAIR_TOKEN alone will not help here — the hostname still rotates.)"
                : "")
        : "Set COMFYUI_MCP_PAIR_TOKEN to a fixed secret to keep this URL working across restarts; " +
            "the pairing listener then also starts automatically at boot, so the phone reconnects " +
            "without opening the panel.";
    return {
        survivesRestart: false,
        rotates,
        note: `This URL stops working when the orchestrator restarts — ${what}. ${cause} ${remedy}`,
    };
}
//# sourceMappingURL=pair-durability.js.map