Skip to main content

Github Copilot–New models added

The list of available models in Github Copilot keeps growing. Whereas last year you could already use GPT-4o, o1, o1-mini and Claud Sonnet 3.5, now you can also try OpenAI o3 and Google Gemini 2.0 Flash.

About Gemini 2.0 Flash

The Gemini 2.0 Flash model is a highly efficient, large language model (LLM) designed for high-volume, high-frequency tasks. It excels in multimodal reasoning, handling inputs like text, images, and audio, and providing text outputs. With a context window of 1 million tokens, it can process vast amounts of information quickly and accurately. Gemini 2.0 Flash is optimized for speed and practicality, making it ideal for everyday tasks, coding, and complex problem-solving.

GitHub Copilot uses Gemini 2.0 Flash hosted on Google Cloud Platform (GCP). When using Gemini 2.0 Flash, prompts and metadata are sent to GCP, which makes the following data commitment: Gemini doesn't use your prompts, or its responses, as data to train its models.

About OpenAI o3

The OpenAI o3 model is a generative pre-trained transformer designed for advanced reasoning and problem-solving tasks. It builds on the capabilities of its predecessor, the o1 model, and is optimized for complex tasks like coding, mathematics, and science1. The o3 model features improved logical reasoning, better memory retention, and enhanced problem-solving capabilities. It also includes a smaller variant, o3-mini, which offers similar functionalities with reduced computational requirements.

Activating these models

If you have an individual Copilot license, you can activate these models using the following steps:

  • On any Github page, click on your profile in the top right corner, and click on Your Copilot:

  • You arrive on the Copilot settings page, where you can enable the new models:

 

If your Copilot license is managed through an organization, you can activate these models using the following steps:

  • On any Github page, click on your profile in the top right corner, and click on Your organizations:

  • Click on Settings for the organization you want to configure.
  • Go to Copilot in the Code, planning, automation section and select Models from the dropdown:

  • Change the settings to Enabled for the models that you want to allow:

 

That’s it!

More information

Multi model support in Github Copilot

Using Gemini 2.0 Flash in GitHub Copilot - GitHub Docs

The next chapter of the Gemini era for developers - Google Developers Blog

Labels:

Popular posts from this blog

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         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more