>> mqlaunch
The best interfaces ask nothing of you.
mqlaunch started as a personal problem: too many tools, too many surfaces, too much switching. A workflow that required remembering where things lived instead of what they were for.
The idea was simple. A single command surface — a prompt — that routes intent to execution. You type what you want to do, not where you want to go. The system handles the rest.
What became clear during development was that the interface itself had to carry no weight. No icons. No menus. No state the user had to manage. Just the cursor and the command.
This is harder to build than it sounds. Reducing the surface means increasing the precision underneath. Every command needs to resolve cleanly, or the whole thing feels broken.
The terminal is not retro. It is honest. It shows you exactly what it can do, nothing more. That constraint is the feature.