Skip to main content

Github Copilot–Auto model select

With the ever growing list of supported AI models in Github Copilot, there is one question that is getting harder to answer.

Which model should I use? 

You can try to safe some money and stay away from the premium request models, but even then you have a lot of options to choose from. You also could check out the model recommendations based on the task you try to achieve but isn’t there a better way?


Enter Auto mode

With the latest update of GitHub Copilot in Visual Studio Code now a new Auto option is available. When you select Auto from the model picker, Copilot will select an appropriate model for you.

 
It is not clear what criteria are used to select a model but you can find out the chosen model at the bottom of the response:

 

Be aware that it is be possible that Auto mode could choose a premium request model, although a discount of 10% is applied when auto mode selects a premium requests model (if you are using a paid plan).

For example, Sonnet 4 would be billed at .9x rather than 1x when using auto model selection.

Remark: Auto mode will only use premium request models with a maximum multiplier of 1.

More information

Auto model selection for Copilot in VS Code in public preview - GitHub Changelog

Supported AI models in GitHub Copilot - GitHub Docs



Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...