Skip to main content

Running a fully local AI Code Assistant with Continue–Part 2–Configuring the VSCode extension

In a previous posted I introduced you to Continue in combination with Ollama, as a way to run a fully local AI Code Assistant. In a first post I showed you how to download and install the necessary models and how to integrate it inside VSCode. We had a look at the chat integration and autocomplete. Today I want to continue by having a look at how we can configure the VSCode Addin.

I originally had planned to write about another feature of Continue, but when I opened VSCode today, I got the following error message:

Whoops! It seems that the configured language model was not available locally on my machine. And indeed when I took a look at the list of installed models, the ‘starcoder2:3b’ model wasn’t there:

Instead I had the ‘starcoder2:latest’ model installed. So let’s use this moment to show how you can configure the Continue VSCode Addin.

Therefore click on the ‘Gear’ icon in the bottom right corner of the Continue chat screen:

This will open a config.json file where we can edit and tweak a lot of the functionality in Continue:

Remark: For the full config.json schema, have a look here.

In our case, we only want to update the model used for the tab autocomplete:

Just hit Save to apply the changes.

Yes! Our autocomplete is back:

Great! Now we can focus on the next post where we take a look at the Edit and Actions features.

Remark: If you encounter any other issue, it is always a good idea to first check the console logs or LLM prompt logs:


 

More information

https://docs.continue.dev/troubleshooting

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

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