Node Navigator (Pythza)

You know the moment: you load a workflow someone shared and the graph is so wide that half of it lives off-screen. You've been scrolling past 80 nodes for five minutes trying to get back to the VAE decode. The Node Navigator is the answer to that specific, very real annoyance - a tiny button that scrolls the canvas straight to any node by its ID.

It's about as minimal as a ComfyUI node gets. One input, one button, no outputs, no inference. Type a node ID, click "Go to node", and the canvas centers on that node instantly. That's the whole feature, and honestly that's the right scope for it. The pack is a single commit from a solo author, MIT-licensed, with no dependencies beyond ComfyUI itself - the kind of thing you install and forget, not the kind of thing that drags in a model download and three conflicting packages.

How it works

Here's the fun bit: the Python side of this node does literally nothing. The class definition returns {} from its function and marks itself an output node, so it's a legal graph citizen, but the actual work happens entirely in the browser. The pack ships a JavaScript file that hooks ComfyUI's frontend (app.registerExtension), finds your node by name, and glues a "Go to node" button widget onto it.

Click the button and the JS looks up the target in ComfyUI's internal node registry, then moves the canvas scroll offset so the target node lands center-screen. No API calls, no keys, no queueing - it's a bookmark with extra steps that you choose the destination of on the fly.

The one input that matters

There's exactly one:

• node_id (INT, default 0, min 0, max 99999) - the ID of the node you want to jump to.

Where do you get an ID? Right-click any node in ComfyUI and the ID is shown at the top of the context menu - that's the author's own tip and it's the reliable way. One gotcha to internalize: node IDs are per-workflow. Copy a node and it gets a new number; delete and re-add and the ID changes. An ID you jot down today is only valid for the graph it came from.

There are no outputs. The node isn't wired into anything and nothing wires out of it - it just sits on your canvas so the button exists. It being marked as an "output node" is a frontend quirk, not a signal that it produces data.

Installing it

Easiest via ComfyUI Manager: search for ComfyUI-Pythza and install. Or the manual route:

cd ComfyUI/custom_nodes
git clone https://github.com/Pythza/ComfyUI-Pythza.git

Then restart ComfyUI. There's no requirements.txt, no model files, no GPU load - it's a frontend widget, so installation is genuinely painless.

Where people get tripped up

• It says "Node #X not found." The ID doesn't exist in the current workflow - mistyped, or you're in a different graph. Open the right workflow or re-check the ID.
• Running the graph does nothing. Correct - it's not a processing node. You don't queue it; you click the button. Thinking of it as a bookmark is the right mental model.
• It's a frontend extension. That means its lifespan is tied to ComfyUI's browser API. If your frontend gets updated hard (ComfyUI's Nodes 2.0 rewrite has already broken many widget-injecting extensions), a single-commit pack like this can stop firing until someone updates it. Not a current problem - just the standing risk for any UI-only node.

One honest caveat: for simple jump-to-node needs, ComfyUI's built-in search (double-click an empty spot on the canvas and type) already gets you around by name. Where the Node Navigator earns its keep is jumping by ID specifically - great for following the numbers in a debugging conversation or a tutorial that says "look at node 137." For persistent, named locations, rgthree's bookmarks are the heavyweight version. This is the middle path: one button, one number, zero dependencies.