Live data from Hacker News

Gorilla-CLI: LLMs for CLI including K8s/AWS/GCP/Azure/sed and 1500 APIs

github.com

11–20 of 73 posts

Re: Gorilla-CLI: LLMs for CLI including K8s/AWS/GCP/Azure/sed and 1500 APIs

#13

It's not a local model. It queries some endpoint on someone else's computer.

Not local yet. Considering the LLM/generative AI velocity we’ve seen, it’s only a matter of time. It’s helpful to see what others build, providing signal it can be built.

If you’re not comfortable using it in your workflow, consider it a peek at what’s to come. Very exciting times. And it's open source.

Re: Gorilla-CLI: LLMs for CLI including K8s/AWS/GCP/Azure/sed and 1500 APIs

#14

It's not a local model. It queries some endpoint on someone else's computer.

Yes indeed. The models are too computationally expensive to run locally (7.5Billion parameters). Though you could in-principle swap in any local model.

Re: Gorilla-CLI: LLMs for CLI including K8s/AWS/GCP/Azure/sed and 1500 APIs

#17

It's not a local model. It queries some endpoint on someone else's computer.

Yes indeed. The models are too computationally expensive to run locally (7.5Billion parameters). Though you could in-principle swap in any local model.

Do y'all have plans to release the model for those who have 16gb graphics cards? (I'm assuming the model is fp16?)

Re: Gorilla-CLI: LLMs for CLI including K8s/AWS/GCP/Azure/sed and 1500 APIs

#18
Loving it! Works nicely for k8s:

  (base)   ~ g get the image ids of all pods running in all namespaces in kubernetes
    kubectl get pods --all-namespaces -o jsonpath="{..imageID}"
  sha256:b19406328e70dd2f6a36d6dbe4e867b0684ced2fdeb2f02ecb54ead39ec0bac0 
  sha256:b19406328e70dd2f6a36d6dbe4e867b0684ced2fdeb2f02ecb54ead39ec0bac0

Re: Gorilla-CLI: LLMs for CLI including K8s/AWS/GCP/Azure/sed and 1500 APIs

#20
post #4

Hi HN, I'm one of the authors from Gorilla Project. Gorilla now presents in an CLI interface and you can interact with your laptop in English! Feedbacks and suggestions are very welcome!!

A flag for printing the chosen command to stdout instead of executing them in a subprocess would be helpful.

Also I am finding in my environment that longer results don't line wrap and so it's hard to tell what the actual full command is, but that might be just me.

Post reply on HN