quick-connections: drawing wires instead of dragging links in ComfyUI

Two ways to draw a link in a node graph

The extension adds circuit board connections and quick connections to ComfyUI, and the two names describe two different behaviours. The circuit board mode is the visual one, where a connection is routed as a line with corners rather than a straight segment between two sockets, so a graph with many parallel links reads like a schematic instead of a bowl of spaghetti. The quick connections mode is the convenience one, where you drag an output toward an empty area and the extension creates the node and the link for you.

Both are implemented as a litegraph extension rather than as ComfyUI-only code, and the README points at the example folder for the standalone version. The package dependencies confirm the shape, with both @comfyorg/litegraph and litegraph.js listed, and the top level of the repository holds a js/ directory for the extension code alongside an __init__.py, which is what ComfyUI uses to register a custom node pack. There is also a .comfyignore file, the convention for excluding files from a ComfyUI package, and a pyproject.toml that carries a [tool.comfy] section with a PublisherId and a DisplayName, which is what the Comfy Registry reads.

Installing it through ComfyUI Manager

The install path is the ComfyUI manager, and it is a lookup rather than a build. The README says to go to ComfyUI Manager and look up quick-connections. There is no pip install, no npm build, and no configuration file to edit, which is a fair description of how ComfyUI extensions normally work.

The second route is the standalone examples, which run the same code against plain litegraph in a browser.

npm install
python -m http.server
# visit in browser: http://localhost:8000/example/quick_conn.html

That serves the example folder over a local HTTP server so the browser can load the module and the example page, which is the quickest way to see the routing behaviour without a ComfyUI install. The repository's package.json carries the scripts behind this, with an example script that runs example/run_example.sh, a docs script that runs example/make_docs.sh, and a lint script that runs eslint over the js/ directory and the example file. The examples will not work on Windows, the README says, because Windows does not support symlinks, and it suggests using WSL instead.

The Comfy Registry metadata points at the same repository and gives the publisher as niknah, with a version of 1.0.29 and the license recorded as MIT License in the pyproject.toml.

The rules that make the routing work, and the one thing it cannot do

The How to use section is short and it is the part that decides whether the extension is usable for you. Do not block the output and input areas, because a route that has nowhere to go is a route the extension cannot solve. Give it some room, since if the connections have no room to move it will get confused, and that is stated as a requirement rather than a suggestion. There is no insert dot in the middle of the connection, so to change a link part way along you drag the output to an empty spot, add a new node, and drag the output of the new node, with an apology attached.

The last constraint is the one that will bite someone used to a schematic editor, where a wire can be grabbed and re-routed at any point. Here the wire is not grabbable in the middle, and the workaround is to break the link and rebuild it through a node.

There is also an off switch. The extension can be disabled in the options under Quick connections, Circuit Board lines, which is the entry for the routing style rather than for the whole extension.

The repository is a ComfyUI package with a browser test rig

The top level of the repository is a ComfyUI extension packaged in the way that registry expects. There is an __init__.py, which is how ComfyUI loads a custom node pack, a .comfyignore file for excluding files from the package, an eslint.config.js with a lint script that runs over the js/ directory and the example file, a js/ directory for the extension itself, and a docs/ directory. The example folder is the part that makes the behaviour testable without ComfyUI: it holds CircuitBoardLines.js and QuickConnection.js as the two pieces of behaviour, a couple of HTML entry points for the ComfyUI and the plain litegraph variants, the corresponding JavaScript, and two shell scripts, run_example.sh and make_docs.sh, wired to the package.json scripts.

The pyproject.toml is where the packaging identity lives, with the project name quick-connections, a description of quick connections and circuit board connections, the version 1.0.29 matching the latest changelog entry, and the license recorded as MIT License. The URLs section points at the GitHub repository, and the comment above it notes that the project is used by the Comfy Registry, which is what the tool.comfy table with PublisherId, DisplayName and an icon URL is for.

The two litegraph dependencies, @comfyorg/litegraph at 0.7.47 or newer and litegraph.js at 0.7.18 or newer, are what let the same extension run in both places. The package.json lists two builds of the same graph library, the scoped @comfyorg/litegraph and the unscoped litegraph.js, at different minimum versions. The extension therefore has to work against both, which is what lets the same behaviour be demonstrated in the browser and inside ComfyUI, and it is also a constraint: the code is written to an interface that exists in two separate builds.

The changelog tells you the extension is still settling

The changelog is the most informative part of the README, and it reads as a list of things that were broken recently. The most recent entry, dated 2026-04-04 for v1.0.29, added adjustable numbers for line and node spacing, which tells you the spacing was hard-coded before that. Before it, v1.0.27 on 2026-03-30 changed error handling to catch errors and continue so that other things that were supposed to happen are not stopped, and v1.0.26 on 2026-03-28 fixed the show and hide links button not working.

The subgraph history is a good illustration of how a graph extension ages. v1.0.21 on 2025-08-29 brought changes to get subgraphs working, v1.0.20 on 2025-08-26 disabled quick connections in subgraphs because it was not working there, and v1.0.19 on 2025-08-23 fixed possible crashes in a subgraph node. Later, v1.0.17 on 2025-07-15 drew connections in subgraph mode. So the feature works now, after a period where it was disabled.

One entry describes a default rather than a fix. The 2024-11-03 note says the extension now defaults to mostly 90 or 45 degree lines, and that this can be changed in the options back to the old way, which is to connect at any angle when nothing is blocking. That is the shape the circuit board look depends on, and it is a setting a user can turn off.

Where quick-connections is the wrong tool

Three cases point elsewhere. The first is a workflow that needs to rewire a connection mid-run. Because there is no insert dot in the middle of the connection, the only way to change a route is to break it and route through a new node, and a graph that is edited constantly will accumulate pointless pass-through nodes. The second is a team that wants a consistent schematic look across tools, since the circuit board rendering is a property of this extension rather than a standard that other node editors share.

The third is a platform other than a browser. The extension is JavaScript running inside ComfyUI's litegraph canvas, and the example route depends on a local HTTP server, so anything that is not a browser page is out of scope.

The alternative worth comparing against is the plain node graph that ComfyUI ships with, where a link is a straight segment between sockets. The difference in approach is that quick-connections adds a routing layer that computes a path around the obstacles, which is what makes a dense graph legible, and it pays for that with the requirement to leave space and the inability to grab a wire in the middle. For a graph with a handful of nodes, the built-in editor is simpler and has no such constraints.

Editorial conclusion

quick-connections fits a ComfyUI user whose node graphs have become unreadable and who wants to route connections like wires on a board, and it also fits a developer who wants to try the behaviour against plain litegraph in a browser. It does not fit a workflow that depends on inserting a connection mid-wire, because the README states there is no insert dot in the middle of a connection, and it does not fit a Windows user trying to run the bundled examples, since the README says the examples will not work there because Windows does not support symlinks and suggests WSL. Before you install it, read the usage notes about giving the connections room to move, since the README says it gets confused when they have none, and check the changelog, because the project fixes subgraphs and toggles often enough that a version older than v1.0.26 will behave differently.

Frequently asked questions

Official sources

1. Issues
2. niknah/quick-connections on GitHub
3. README