Cline & Roo Code
Two VS Code extensions with the same settings and the same shape: an agent in a side panel that reads your workspace, proposes edits and runs commands, with a diff to approve at each step. Roo Code is a fork of Cline; configure it identically.
Install
Install Cline from the VS Code marketplace (or Roo Code — the configuration below is the same for both).
Configure
Open the extension’s settings and set:
| Setting | Value |
|---|---|
| API Provider | OpenAI Compatible |
| Base URL | https://api.devotel.com/v1 |
| API Key | dvt-YOUR_KEY |
| Model ID | kimi-k3 |
Pick OpenAI Compatible, not “OpenAI”. The plain OpenAI provider ignores your base URL and
sends requests to OpenAI, where a dvt- key means nothing.
Using it
Open the Cline panel and describe the task. Cline has two modes, and the distinction is worth learning:
- Plan — it reads the code and proposes an approach, without editing anything. Cheap, and a good way to check it has understood the task before it starts writing.
- Act — it carries the plan out, asking you to approve each file edit and each terminal command.
Edits arrive as diffs in the editor, so reviewing an agent’s work is the same as reviewing a colleague’s.
Both extensions work in any VS Code fork — VS Codium, Cursor, Windsurf — since they only need the extension host, not the editor’s own AI features.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
401 | Key not saved, or pasted with whitespace; re-enter it |
| Requests go to OpenAI | Provider is “OpenAI” rather than “OpenAI Compatible” |
404 / model_not_found | Model ID must be exactly kimi-k3 |
| Long pause before any output | Expected — kimi-k3 reasons before it answers; see Models |
429 | Rate limit; see Rate Limits & Errors |