Skip to main content

Running a fully local AI Code Assistant with Continue–Part 3–Editing and Actions

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.
A second post was focused on the configuration part (and a little bit of troubleshooting).

Today I want to continue by having a look at 2 other features; edit and actions.

Editing

The editing feature allows you to select a piece of text and describe how it should be changed. The nice thing about this feature is that you can use without leaving the code file or block you are working on.

Just select a piece of code and hit CTRL-I. We now get an Edit popup where can enter our prompt(or select an existing prompt):



Hit submit to get an answer back:

Now you get a list of suggested code changes that you can accept or reject:

Remark: Depending on the model you are using, the quality of the result can differ and also the waiting time can be largely different. I noticed it worked best when I kept the selected snippets small.

It feels somewhat similar to the inline chat functionality you get when using Github Copilot.

Actions

Actions allow you to invoke common use cases without having to write a full prompt. For example, creating a unit test, adding some documentation, …

To invoke an action type '/' and you get a list of available actions:

Select the action you want to execute from the dropdown and hit enter:

This feature can be found in Github Copilot as well as slash commands:

The nice thing in Continue is that you can easily create your own actions.

Therefore you need to take the following steps

  • Enter ‘/’ again and this time select Build a custom prompt:

  • A .prompts folder is created and a new prompt file is added. Change the name so that it matches the name you want to give the action.

 

 

If we now type ‘/’ again, our custom action becomes available:


Remark: I noticed that Continue sometimes didn’t immediately picks up the name change. In that case restarting VSCode helps.

Great! Let’s continue this series tomorrow. Already looking forward on what feature(s) we’ll discover then.

More information

Docs | Continue

https://devblogs.microsoft.com/visualstudio/mastering-slash-commands-with-github-copilot-in-visual-studio/
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