Skip to main content

Running a fully local AI Code Assistant with Continue–Part 1–Introduction

When I‘m coding, I'm assisted today by Github Copilot. And although Github does a lot of effort to keep your data private, not every organisation allows to use it. If you are working for such an organisation, does this mean that you cannot use an AI code assistant?

Luckily, the answer is no. In this post I’ll show you how to combine Continue, an open-source AI code assistent with Ollama to run a fully local Code Assistant. Keep reading…

Note: This post is part of a bigger series. Check out the other posts here:

What is Continue?

Continue is an open-source AI code assistant that can be easily integrated in popular IDEs like like VS Code and JetBrains, providing custom autocomplete and chat experiences.

It offers features you expect from most code assistants like autocomplete, code explanation, chat, refactoring, ask questions about your code base and more and all of this based the AI model of your choice.

Installing and configuring Continue in VSCode

As mentioned in the intro you can integrate in both VS Code and JetBrains IDEs like Rider or IntelliJ. In this post I’ll use VSCode as an example but I welcome you to check the documentation if you want to use it in your favorite JetBrains IDE.

  • Open VSCode and click on Extensions in the sidebar: 


  • Search for Continue and click on Install:

  • After the installation has completed, you get a welcome page. Here you can also select a configuration. Choose the Local Models option and click on Continue:

  • On the next page, it helps you to set up your local LLM using Ollama. I already had Ollama installed and some models available, so I completed the process by clicking  on Complete onboarding:

 


  • It is also recommended to move Continue from the left sidebar to the right so that we can keep using the file explorer at the same time:

Let’s give Continue a try

Start by opening a codebase in VSCode.

Let’s first try to ask some information about our code. Highlight a specific piece of code and hit CTRL-L. The code becomes part of the chat window and we can now ask questions about it:

 


Cool! Let’s now see the autocomplete in action. Put the cursor somewhere in your code and hit TAB:

That’s a good start!

In a next post, we dive deeper in some of the other options that Continue has to offer.

More information

Continue

continuedev/continue: ⏩ Continue is the leading open-source AI code assistant. You can connect any models and any context to build custom autocomplete and chat experiences inside VS Code and JetBrains (github.com)

An entirely open-source AI code assistant inside your editor · Ollama 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