For developers who live inside log files, lnav is already a sharp tool. But it is far from finished. Every missing feature slows down analysis. Every extra keystroke is wasted focus. That’s why talking about the right lnav feature requests isn’t just an idle wishlist—it’s a roadmap for making log navigation lighter, faster, and smarter.
The most common request is real-time streaming from multiple sources without manual refresh. Imagine piping in structured and unstructured logs side by side, filtered instantly, with queries running live. This means no switching contexts, no scrolling endlessly, and no digging through files just to catch a single event.
Another high-value request is better JSON awareness—richer parsing, inline collapsing, and the ability to write quick expressions against nested data. Logs today are rarely flat. Recognizing the structure without forcing a full schema is essential for speed.
Next is unified search across sessions. When you’ve burned hours finding a rare error once, you shouldn’t have to hunt for it again. Persistent queries, quick recall, and cross-file matches would turn lnav into a true investigative console.
Then there’s the dream of deeper integrations. Seeing metrics, annotations, and deployment markers alongside logs removes the guessing between code changes and observed behavior. An event doesn’t happen in isolation—it has context. And lnav should make that context obvious.
Finally, performance matters. Logs grow fast, both in volume and complexity. Faster indexing, disk-efficient storage, and safe parallel parsing will keep lnav working at the speed of thought, not the speed of I/O. Meeting this demand is not a luxury—it will decide if the tool remains viable for heavy use.
Every one of these lnav feature requests can be prototyped, tested, and delivered in an environment that feels real. The fastest way to prove what works is to skip theory and build running versions in minutes.
That’s where hoop.dev comes in. You can see your own lnav improvements live before you’d normally get a pull request out for review. Test the new features on real logs, collaborate instantly, and know in hours—not weeks—if your change is worth shipping. Build it, run it, refine it—without waiting.
The next killer feature might already be in your head. Stop waiting for a ticket to get picked up. Make it real and see it live today.