OpenAI-compatible

Use a model with Continue through IteraCompute.

Use open models in your IDE.

Connect in three steps

1. Create an API key

Create or sign in to your IteraCompute account, then create a key in the Console.

2. Configure the base URL

Use provider: openai with apiBase and useResponsesApi: false. These chat, edit and apply roles use Chat Completions.

3. Select the model

Use the exact API Model ID for your chosen model. Check its context and capabilities before enabling agent or vision features.

Choose your model

Example configuration

Keep API keys in your server environment or tool credential store. Replace the example key field with your own key where applicable.

~/.continue/config.yaml
name: IteraCompute
version: 1.0.0
schema: v1
models:
  - name: Qwen3.8-27B
    provider: openai
    model: qwen/qwen3.8-27b
    apiBase: https://api.iteracompute.com/v1
    apiKey: ${{ secrets.ITERACOMPUTE_API_KEY }}
    useResponsesApi: false
    roles: [chat, edit, apply]
    capabilities: [tool_use, image_input]
    defaultCompletionOptions:
      contextLength: 131072

Version and verification

Configuration reference · reviewed 2026-10-15. A reproducible end-to-end tool test has not been recorded here. Record your installed version and test date when running the steps below.

Success criterion

Send a chat prompt in Continue, then request one small edit. Check the actual diff and run the relevant test.

Record the installed version
VS Code → Extensions → Continue → Version

Test the configured tool itself after the API check below. An HTTP 200 or a cURL result alone does not verify that tool.

Test the connection

cURL · Chat Completions
# Bash / zsh / WSL; set ITERACOMPUTE_API_KEY in your environment first.
curl --fail-with-body https://api.iteracompute.com/v1/chat/completions \
  -H "Authorization: Bearer $ITERACOMPUTE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"qwen/qwen3.8-27b","messages":[{"role":"user","content":"Reply with exactly: Hello!"}],"max_tokens":512}'

Check that choices[0].message.content contains visible text; HTTP 200 alone is insufficient. Reasoning may consume the output budget. For free Qwen, use the first free call example to disable thinking, then send a prompt inside your tool.

Selected model capabilities

These are API capabilities of the selected model. Feature availability in your workflow also depends on the tool and its settings; reasoning controls vary by model.

  • Chat CompletionsSupported
  • Tool callingSupported
  • ReasoningSupported
  • Image inputSupported
  • StreamingSupported

Troubleshooting

Configuration not loaded

Merge the example into ~/.continue/config.yaml and check the YAML indentation. Store the key in ~/.continue/.env with the same name used by the secrets expression.

Wrong endpoint or role

Use provider: openai, apiBase ending in /v1 and useResponsesApi: false. These chat, edit and apply roles are not an autocomplete configuration.

Chat works, edits do not

Check the selected role and tool_use capability. Test a small edit, review its diff and run its test; a chat reply alone does not verify editing.

429 / Request limits

Check account-wide monthly usage and TPM. Honor Retry-After and avoid parallel retries. Free Qwen has no automatic paid overage; other models use their published prices.

401 / 403: check the key and model permission. Free Qwen requires no balance or card. For paid models, also check available balance.

Continue configuration reference →

Start building with Continue.

Connect your key, choose a model and send your first request.