Skip to main content
Connect OverControl to Cline and use OverControl models directly inside your coding workflow. Cline is an AI coding agent that can help you understand a codebase, edit files, run commands, inspect errors, and complete development tasks from your editor. This guide shows how to configure Cline with OverControl using an OpenAI-compatible setup.
This guide focuses on the Cline editor setup. Cline is available across multiple developer environments, but custom provider settings may vary depending on the platform.

​
Where you can use Cline

Cline is available in several developer environments.
Start with the editor integration. It is the clearest path for connecting OverControl to Cline with a custom endpoint.

​
Before you start

You need:
  • an OverControl account;
  • an OverControl API key;
  • the OverControl Base URL;
  • one OverControl model ID;
  • Cline installed in your editor.

Get your API key

Create an API key before connecting OverControl to Cline.

​
Step 1: Install Cline

Install Cline in your editor.
1

Open your editor

Open VS Code, Cursor, Windsurf, VSCodium, or a supported JetBrains IDE.
2

Open extensions or plugins

In VS Code-style editors, open the Extensions panel. In JetBrains IDEs, open the Plugins marketplace.
3

Search for Cline

Search for Cline and install the official extension or plugin.
4

Open Cline

After installation, open Cline from the editor sidebar or command palette.

​
Step 2: Open Cline settings

Open the Cline panel and go to settings. The provider settings are where you choose which model provider Cline should use.

​
Step 3: Select OpenAI Compatible

In Cline settings, choose OpenAI Compatible as the API provider. This option lets Cline connect to providers that expose an OpenAI-compatible endpoint.

​
Step 4: Enter the OverControl connection values

Enter the OverControl values in the provider fields.
Use gamma-2-fast for setup testing and everyday coding help. Use gamma-2-max for complex reasoning, larger context, architecture work, and harder debugging.
Keep your API key private. Do not share it in screenshots, commit it to a repository, or paste it into public chats.

​
Step 5: Save and test the connection

Save the provider settings. Then send a simple test prompt in Cline:
If Cline responds using the selected OverControl model, the integration is working.

​
How to use Cline with OverControl

Once connected, use Cline for focused coding tasks. Good tasks include:
  • understanding a new codebase;
  • explaining a file or function;
  • planning an implementation;
  • debugging an error;
  • reviewing a change;
  • refactoring code;
  • writing tests;
  • improving documentation.
Cline may ask to read files, edit files, run commands, or inspect project output. Review each action before approving it.
1

Start with one task

Give Cline a specific coding task, bug, file, or question.
2

Ask for a plan first

For larger changes, ask Cline to explain the plan before editing files.
3

Approve actions carefully

Review file reads, edits, terminal commands, and browser actions before approving them.
4

Review the diff

Check the code changes before accepting or committing them.
5

Run tests

Ask Cline to run the relevant test, build, or lint command when appropriate.

​
Troubleshooting

Check that the OverControl API key was copied correctly and has not been revoked. Create a new key if needed.
Check that the Base URL is correct and that your network allows the connection.
Make sure the model ID is copied exactly.
Make sure you are using a Cline surface that exposes custom provider settings.
Check your plan, usage allowance, API access, model ID, Base URL, and API key.

​
Next steps

Get your API key

Create and manage your OverControl API key.

Models

Choose the right model for Cline.

Integrations overview

Return to all supported integrations.