Configure Cline with ScriptEngine.

Scope

Use Cline's generic compatibility path

Cline documents a generic OpenAI Compatible provider for endpoints that follow the OpenAI API shape. The required fields are a base URL, an API key, and a model ID. ScriptEngine publishes that base URL and bearer-authenticated chat-completions surface.

This page verifies the connection path, not every Cline capability. Cline can request tools, structured outputs, images, and large context depending on the configured model. ScriptEngine has not published a universal guarantee for those fields. Start with a text-only request, then test the exact capability your project needs before giving an agent permission to edit files or run commands.

The configuration steps below follow the official Cline OpenAI Compatible documentation.

Model discovery

Use a model ID that your key can actually see

Before opening Cline, query the ScriptEngine model endpoint. The result is the source of truth for the model string you should paste into Cline. The public model catalog is useful for price comparisons, but account-level availability may change.

export SCRIPTENGINE_API_KEY="YOUR_PRIVATE_KEY"
curl https://scriptengine.org/v1/models \
  -H "Authorization: Bearer $SCRIPTENGINE_API_KEY"

Copy one returned ID as MODEL_ID_FROM_DISCOVERY. Do not add a provider prefix unless Cline specifically asks for one; its OpenAI Compatible form normally expects the model ID accepted by the configured base URL.

Cline settings

Enter the ScriptEngine connection values

1. Open Cline in VS Code or the Cline interface.
2. Open the provider or API settings panel.
3. Set API Provider to OpenAI Compatible.
4. Set Base URL to https://scriptengine.org/v1.
5. Paste your private ScriptEngine key into API Key.
6. Enter the model ID returned from /v1/models.
7. Leave image support, computer use, and tool-related options off for the first text test unless you have separately verified them.
8. Use Cline's connection verification action if your release provides it.

Smoke test

Ask for a harmless fixed response

Start a new Cline task with a message that does not request file edits, shell commands, or external tools. For example: Reply with exactly “ScriptEngine connected” and do not call tools. A normal answer confirms that the URL, key, model, and basic chat request are aligned.

curl https://scriptengine.org/v1/chat/completions \
  -H "Authorization: Bearer $SCRIPTENGINE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"MODEL_ID_FROM_DISCOVERY","messages":[{"role":"user","content":"Reply with exactly: ScriptEngine connected"}]}'

Capability boundaries

Test agent features separately

Cline exposes model settings for context window, output tokens, images, computer use, and token price. Those fields describe what Cline can configure; they do not make a ScriptEngine route support the capability automatically.

• Text chat: verified public integration path.
• Streaming usage metadata: confirm the exact response before relying on token accounting in a stream.
• Tools and computer use: not a universal ScriptEngine promise; test a harmless tool schema against the selected model first.
• Images: only enable when the model catalog and endpoint have been verified for image input.
• Reasoning controls: model-specific; do not copy provider-specific parameters blindly.

Use the API integration overview for the supported request shape and the support page for safe diagnostic information. ScriptEngine currently publishes no uptime or response-time SLA.

Troubleshooting

Separate Cline settings from API errors

Invalid API key

Run the model-list cURL request from the same machine and compare the key source. Cline must receive the ScriptEngine API key, not the account login password.

Model not found

Replace the model with an ID returned by the same key. A public catalog entry may be unavailable to a key or may have changed.

Connection refused or 404

Check that the base URL is exactly https://scriptengine.org/v1 and that no second /v1 or endpoint path was appended.

Text works but tool use fails

Keep the text provider configuration. Disable the unverified capability and test it independently; a tool failure does not mean the basic provider connection is broken.

Sources

Recheck the client and route when either changes

This guide was checked August 4, 2026 against Cline's official OpenAI Compatible provider documentation and ScriptEngine's public API contract. Cline releases may adjust labels and optional model fields; use the current official documentation when an interface differs.

• Cline OpenAI Compatible provider
• ScriptEngine API integration overview
• ScriptEngine model catalog and rates
• Affordable OpenRouter alternative comparison