Continue.dev

Continue.dev points each config.yaml model entry at Gateway’s OpenAI-compatible endpoint. Shared setup: Building with coding agents.

Configure Continue

Open ~/.continue/config.yaml (VS Code: Continue panel → gear icon → Configure) and add entries with provider: openai and apiBase set to Gateway.

name: My Config
version: 0.0.1
schema: v1
models:
  - name: Claude Opus 5 (Gateway)
    provider: openai
    model: anthropic/claude-opus-5
    apiBase: https://api-gateway.merge.dev/v1/openai
    apiKey: ${{ secrets.MERGE_GATEWAY_API_KEY }}
    roles: [chat, edit, apply]
    capabilities: [tool_use, image_input]
    requestOptions:
      headers:
        X-Merge-Thread-Id: continue-alice

Set MERGE_GATEWAY_API_KEY in Continue’s secrets, or paste the key inline for local-only use. Reload (VS Code: Developer: Reload Window, JetBrains: restart the IDE) and pick the model in the panel. For an alias, use model: "@alias/support-agent", quoted because YAML reserves a leading @.

Gotchas

• Add tool_use to capabilities only for models that support tool calling
• The embed role works through /v1/openai/embeddings. Gateway has no rerank endpoint, so don’t assign it the rerank role.
• Give autocomplete only a small, fast model, since it fires on every typing pause
• Continue sends no session header, so the optional requestOptions.headers above groups your requests into one thread in Logs
• With an organization key, attribute an entry to a project via requestOptions.extraBodyProperties with project_id (the project’s UUID) and optional tags as {key, value} pairs

Next steps