Nutanix in your terminal.

I come from the Kubernetes world, where k9s is how I get work done: a colon prompt, contexts I switch in one command, tables I move through without taking my hands off the keyboard. I also look after several Nutanix environments, and nothing like that existed for them. Prism Central is a browser tab. The command-line tools that do exist, ncli, acli and nuclei, run on the cluster itself and need an SSH session before you can type anything.

So I built the thing I wanted: that way of working, pointed at Prism Central. Switching environment is one command. A table tells me what I need without a detour. And I never copy a UUID from one screen into another, because wherever the API hands back an identifier, Nutsh shows me the name.

The other half of it is restraint. Moving fast in production is fine right until it is not, so the things that change state sit behind more friction than the things that only read.

None of it was meant to leave my laptop. This is a pet project, written on evenings and weekends for an audience of one. A friend I showed it to made the point that plenty of other people look after Nutanix through the same browser tab I was trying to escape, and that keeping it to myself was a waste. That is the only reason there is a repository and a website.

It is also, and I would rather say so than let you wonder, built with a lot of AI assistance. I wrote the mockups and the rules about what it must never do, and Claude wrote most of the rest. I review and adapt what comes back before it goes anywhere near my lab or a client environment, and the safeguards against an accidental deletion were designed by a human, not generated. It has been running on my own laptop, against my own lab, for a few months now. The tests, the guard rails and the reasons behind them are all in the repository, and they are what I would judge it on.