Skip to main content

Connect Cline with a guided setup →

The guided connect page mints your key, hands you every value to paste, lists the model IDs with their context-window and vision details, and confirms the moment your first task runs.
Everything below is the manual equivalent. Cline configures its provider inside VS Code — there is no settings file to edit, so this is a one-time paste stored in VS Code’s secure storage (Cline’s OpenAI Compatible guide). Open Cline, click the settings gear in its panel, and under API Configuration set: Claude models work through the same OpenAI Compatible entry — the gateway bridges them — so one provider entry serves the whole catalog. Cline keeps a single active model; swap the Model ID whenever you like. Any id from Models works, for example:
Keep the /v1 suffix on the base URL. Cline appends /chat/completions to it — without /v1 every request 404s.

​
Optional: model configuration

Cline’s optional model configuration fields (context window, max output tokens, supports images) default conservatively. Set them to the values in the table above — the guided page shows them per model — if you want Cline’s own context-limit warnings to be accurate on long tasks.

​
Verify

Start any task in Cline (for example, “explain this file”) with the OpenAI Compatible provider active and watch it stream. The request appears on your usage page seconds later — metered and billed to your organization’s wallet.

​
Forks take the same values

Roo Code and other Cline forks expose the identical OpenAI Compatible provider fields — reuse the base URL, key, and model IDs above there, or follow the Roo Code guide.