I started building it because I kept feeling that most API tools work well for single requests, but become much less helpful once the work turns into an actual flow. The moment you need to chain requests, reuse variables from previous responses, understand dependencies, or debug failures step by step, the experience gets much more fragmented than it should be. Luzo is my attempt to make that workflow layer feel more natural. I wanted something that lets you design API flows visually, see how data moves between steps, and inspect execution as it happens instead of piecing everything together from logs. I d especially love feedback on three things: whether the workflow model feels intuitive, whether the execution timeline helps with debugging, and whether the desktop-first direction makes sense for this kind of tool.
Luzo is a desktop-first, open-source tool for building, running, and debugging multi-step API workflows. Instead of treating requests as isolated calls, it lets you design dependency-aware flows, pass variables between steps, inspect execution through a live timeline, and retry from failure without restarting everything. Built for developers and QA teams working with real API workflows, not just single requests.