Should I create a k9s style TUI for NATS?

I use k9s a lot. It is one of those tools that quietly changes how you work once it becomes part of your day. So every now and then I catch myself thinking about what a k9s style TUI for NATS would look like, especially when I am moving around streams and consumers and wishing I had a faster way to see what is going on.

Part of the idea is probably just familiarity. k9s works so well that it is tempting to project the same shape onto every system you use. I keep wondering whether NATS has enough moving parts to justify that kind of interface, or whether I just want it because I already like the pattern.

The place where it starts to feel more real for me is JetStream. Once there are streams, consumers, lag, redeliveries, and a bunch of state that only makes sense when you can see it changing, the idea gets more interesting. That is usually the moment when I start thinking a live terminal view could actually help instead of just looking nice.

I am still not sure. Maybe the answer is yes and the tool ends up being genuinely useful. Maybe the answer is no and the nats CLI is already enough. Right now it just feels like one of those ideas that keeps hanging around because there might be something there.