Cline

Cline is a VS Code extension that edits files and runs commands for you. It ships a generic provider called OpenAI Compatible, which is exactly what Helmcode needs.

Configuration

1. Open Cline’s settings

In VS Code, open the Cline panel and go into its settings with the gear icon.

2. Choose the provider

In API Provider, select OpenAI Compatible.

3. Fill in the three fields

Warning: the base URL ends at /v1. This is the most common mistake with this provider: pasting https://api.helmcode.com/v1/chat/completions instead of just the base. Cline appends the endpoint part on its own, so with the full path you would end up calling an address that does not exist.

4. Declare what the model can do

Cline asks because with a generic provider it has no way of finding out:

Every language model Helmcode serves takes images and does tool calling, so those two boxes are ticked whichever you pick. What changes between them is the window and how deep the reasoning goes.

5. Try it

Open a folder with code and ask it for something small and observable — for instance, to read the README and summarize what the project does. If it answers and asks for permission to touch files, it is connected.

Recommended model

glm5.3-flash. It holds the long rounds of reading, editing and reading again that Cline does, on a 1M window, and it is in every plan’s quota. deepseek-v4-flash is the alternative at the same size.

Known issues

• Cline eats a lot of context. It sends file contents on every turn, so it spends tokens far faster than a chat does. Check your key’s limits in Rate limits and your usage in the console.
• The four fields have to come from the same place. Provider, base URL, key and model, all Helmcode. Mixing a key from one place with a base URL from another always gives a 401.
• Roo Code and the other derivatives are configured the same way. They are Cline forks and have the same generic provider, with the same four fields.