Selecting up and down stream nodes without backward/forward traversal

Hi There,

This is going to be about the shift-click feature:

Screen Recording 2026-10-16 at 10.25.56

  • Shift & click in the middle of a node: all reachable nodes are highlighted.
  • Shift & click on the right side of a node: all reachable downstream nodes are highlighted.
  • Shift & click on the left side of a node: all reachable upstream nodes are highlighted.

The issue I have is the "reachable", this implies a backward or forward traversal of the node graph. In this case, the left click also highlights the upper branch, but what I want is only connected nodes, so that that left click should result in:

Similarly if I connect nodes "function 22" with "function 29" and then do a right click, I get this:

but what I want is this:

Only the downstream nodes are highlighted.

I'm not wanting to change the existing behaviour, that behaviour is very useful for certain use cases but what I would like is a modifier key that only highlights connected nodes, i.e, those that are reachable directly and without recursive traversal.

Modifiers already exist. The cut tool (option key + click + drag) to highlight multiple links that will be cut:

Can be modified (something that I learnt after implementing the feature myself!) by adding a shift to insert a junction:

Which is incredibly useful btw!

So what I suggest is adding a modifier to the shift and click, i.e., the option key, and have the behaviour be modified so that only connected nodes are highlighted.

Where does that feature come from? I am not seeing it myself.

Builtin since at least v4.

What happens if you shift+click (i.e. hold the shift key and click) on a node?

If that highlights everything, then you know it's working. Then move to the left or right side of the node and repeat.

This is on a mac but even windows has a shift key :wink:

I think I need to scrap my dev instance, it is giving me different results to live. It is working on my live instance.

I've recently developed another issue on my dev instance as well. Restarting Node-RED completely results in a delay of at least 2 minutes before things become properly responsive. So something is blocking the loop somewhere.

Indeed, switching projects on my dev instance also works, just not on my "normal" dev project. Strange. So it is the project rather than the instance that has issues.