Two Keys Come Home
Space opens the node browser and Tab opens fuzzy search, exactly as the empty canvas has been promising all along. The two fastest routes from idea to node now actually exist under your fingers, and the cue transport politely waits for its own panel before borrowing the space bar.
Open a fresh patch in Lux and the empty canvas offers you a single line of advice: press Space to add a node, Tab to search. It is good advice. It is the advice every patching environment converges on, because when an idea arrives you want a node under your cursor in the time it takes to think it. There was just one problem, and if you have used Lux for more than four minutes you have already met it: neither key did anything.
This release is the one where the hint stops being aspirational.
Where the space bar actually went
Space was not broken. It was busy. Deep in the keyboard routing, the live performance system had claimed Space as its GO key, the big one, the press-this-and-the-next-cue-fires key, and it claimed it globally, swallowing the keystroke before the canvas ever heard about it. The logic was generous in spirit: a performer running a set full-screen should be able to slam Space without checking what has focus.
A closer look made the arrangement harder to defend. The cue panel that GO belongs to does not currently have a way to be opened. So the editor’s single most advertised gesture was being donated, wholesale, to a feature you could not reach, and what you got for pressing Space was a precisely engineered nothing.
The transport keys still exist, Space and J and K, but they now answer only while the cue panel is actually open. Performers lose nothing: panel up, Space is GO, exactly as before. Patchers gain the key the canvas always claimed they had. Two audiences, one space bar, no more quiet theft.
Tab, meanwhile, was redecorating
Tab had a different captor. The UI toolkit underneath the editor treats Tab as sacred furniture-hopping: press it and focus politely moves to the next widget. Helpful in a settings form. Less helpful when the “next widget” is the File menu and what you asked for was the node search box. The toolkit consumed every Tab before the editor saw it, without exception, which is why pressing Tab over a perfectly blank canvas highlighted a menu you did not want.
Now, when nothing is actually typing (no text box focused, no field waiting for input), Tab skips the furniture tour entirely and goes straight to the canvas, where it opens fuzzy search at your cursor. If you are mid-edit in a text field, Tab still behaves like Tab. The rule is the one you would write yourself: keys belong to whatever you are clearly doing.
Trust, but verify, then verify again
The sour note in this story is that tests existed for both gestures and they passed the whole time. They tested the canvas’s reaction to the keys, but called the canvas directly, stepping around the routing layer where the interception lived. The lock worked; the test was checking the door handle.
So the routing layer itself is now the thing under test: press Space at the router, watch the Create Node dialog open; press Tab, watch search appear; open the cue panel, press Space, watch GO fire instead. The same table the live keyboard path uses, exercised end to end, plus a session of actually pressing the keys in the running editor and watching the right windows appear, which remains the most honest test there is.
What it buys you
The distance from thought to node is now two keystrokes shorter, which is to say it finally matches the brochure. Space, type three letters, Enter, and the node is on your canvas. It joins search everywhere as the second hand on the instrument, and it means the first sixty seconds of Lux behave the way the welcome screen says they will. Small keys, large difference.