Skip to main content

Running a fully local AI Code Assistant with Continue–Part 4– Learning from your codebase

In a previous posted I introduced you to Continue in combination with Ollama, as a way to run a fully local AI Code Assistant.

Remark: This post is part of a bigger series. Here are the other related posts:

Today I want to continue by having a look at how continue can learn from your codebase and provide suggestions based on that.

But before I can show you this feature we first need to download an embedding model. Embedding models are models that are trained specifically to generate vector embeddings: long arrays of numbers that represent semantic meaning for a given sequence of text. These arrays can be stored in a database, and used to search for data that is similar in meaning.

We’ll use the nomic-embed-text embeddings, so let’s download that one:

ollama pull nomic-embed-text

Now we need to update the Continue configuration by changing the config.json file.

  • Click on the gear icon in the bottom right corner of the Continue window:

 


  • The config.json file is loaded. Scroll to the bottom to find the embeddingsprovider section. Update it with the following information:

 


  • Don’t forget to save the file to apply the changes.

Now continue will index the code(this can take some time depending on the size of your codebase). But once that is done, you can  start using the @codebase context provider to use this information.

For example, we can use it to generate a new class based on existing classes in your code:

 


Here is the result:


Nice!

More information

https://docs.continue.dev/customize/deep-dives/codebase

https://ollama.com/blog/embedding-models

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