That gut-sinking moment when you realize your entire debugging trail might be a work of fiction is where Lnav Recall changes the game. It isn’t just about reading logs—it’s about remembering them, searching them, replaying them, and stitching the truth together when everything else is noise.
Lnav Recall takes lnav, the beloved terminal log navigator, and makes it persistent. Every log you’ve tailed, every session you’ve parsed, every query you’ve run—it’s there. Not streamed once and gone forever, but stored, indexed, and ready to search again tomorrow, next week, or next quarter.
With Recall, you can query across days of logs without touching brittle shell history or writing the same grep pipeline three times before lunch. You can see the entire conversation a single request had with your systems, even if it hopped across multiple services. Context is brutal to rebuild from scratch; Recall makes it permanent.
Unlike plain lnav, Recall doesn’t ask you to keep logs open indefinitely. You can quit, close your laptop, move on to something else—your logs will be there when you return. It turns ephemeral insight into an archive. A searchable, filterable, session-aware archive that feels as immediate as a scrolling terminal.
If your observability stack feels bloated or slow, Lnav Recall is quick, local-first, and built for speed. It doesn’t challenge your production metrics pipeline—it complements it. From zero to indexed, it’s seconds, not hours. From query to answer, it’s instant.
Once you use Recall, you stop dreading restarts. You stop fearing that the search you run now will be impossible to repeat six hours later. You start asking better questions, because the answers are already there.
Want to see Lnav Recall in action without wasting a day setting it up? Spin it up live in minutes at hoop.dev and keep every log worth remembering.