Motorway 2x0
Motorway 2x0
- MOTORWAY ππ¨
- ANY_(A)
- ANY_(B)
- MOTORWAY ππ¨
Motorway 2x0 is the write-only node in agilly1989's Motorway pack, and honestly it's easy to miss precisely because it does so little on screen. The "2x0" means two inputs and zero data outputs. It swallows two values, tags them with keys, and keeps the bus rolling - that's the whole job. If you've ever wished you could just stash a couple of numbers or strings somewhere mid-workflow and grab them three branches later without dragging wires across the canvas, this is that somewhere.
The Motorway pack is a beta "pipe" implementation by solo dev agilly1989 - the pipe-equivalent of rgthree's Context nodes or Impact Pack pipes, but instead of passing a dict it passes a custom MotorwayClass bus object down one wire. The bus connection is called MOTORWAY ππ¨, and it's genuinely a bus: it shows up as one required input on every node, and one output that continues the route. You must start any flow with MotorwayStart (or one of the Motorway primitive nodes, which can also act as a start), then drive the bus through as many junctions as you like.
How it works
You connect two values to ANY_(A) and ANY_(B). For each one you also fill in a key - ANY_(A)_key and ANY_(B)_key. Whatever you type, like denoise or seed_int, gets attached to that value and stored on the bus. Under the hood the pack sha256-hashes your key into an attribute name (hash_β¦), which is why missing-key errors look like 'MotorwayClass' object has no attribute 'hash_' instead of a friendly "key not found". Storing the same key again later, anywhere on the route, overwrites the old value.
Since 2x0 has no data outputs, it's a pure sink: its only output is the continued MOTORWAY ππ¨ bus. You'd chain it into a branch where you want to record state without immediately using it - write cfg and steps here, then read them at the sampler on a completely different part of the graph with a node like Motorway 2x0's cousins that have outputs. That read doesn't need to happen in the same branch, just anywhere downstream on the same bus.
Installing
cd ComfyUI/custom_nodes
git clone https://github.com/agilly1989/ComfyUI_agilly1989_motorway
then restart ComfyUI. It's also in ComfyUI Manager under ComfyUI_agilly1989_motorway. No pip packages, no model files, nothing extra to download - it's a handful of pure-Python node classes.
Common issues
- The
hash_missing-attribute error means the key you asked for was never written, or was written with a different string. Remember keys are matched exactly, spaces and casing included. - If you type a key into
ANY_(A)_keybut leaveANY_(A)disconnected, the node storesNoneunder that key - which silently erases anything already there. Only fill keys for inputs you've actually wired up. - Since there are no data outputs, beginners often think it's broken when they can't find a value coming out. There isn't one. Read the value downstream instead.
The pack is beta and the author cheerfully warns things may break. But for tucking two values onto a bus and walking away, 2x0 is the node you'll reach for.
Inputs (5)
| Name | Type | Default | Description |
|---|---|---|---|
| MOTORWAY ππ¨ | MOTORWAY ππ¨ | β | |
| ANY_(A)opt | * | β | |
| ANY_(B)opt | * | β | |
| ANY_(A)_keyopt | STRING | β | |
| ANY_(B)_keyopt | STRING | β |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| MOTORWAY ππ¨ | MOTORWAY ππ¨ | β |