Continue CLI

Continue CLI (cn) uses the same config.yaml schema as the Continue IDE extension.

config.yaml

~/.continue/config.yaml (or cn --config ./my-config.yaml):

name: Yaha Gateway
version: 1.0.0
schema: v1

models:
  - name: Yaha Chat
    provider: openai
    model: gpt-4o
    apiBase: https://gateway.yahagateway.io/v1
    apiKey: yaha.<your-project-key>
    capabilities:
      - tool_use
    roles:
      - chat
      - edit
      - apply

Agent mode

Custom OpenAI-compatible endpoints require explicit tool support:

capabilities:
  - tool_use

o-series / GPT-5 models

If Continue uses the Responses API for a model, ensure Yaha proxies /v1/responses or set:

useResponsesApi: false

when the gateway should use /v1/chat/completions instead.

MCP (Tool Bridge)

Add to config.yaml:

mcpServers:
  - name: nova-tool-bridge
    command: npx
    args:
      - -y
      - mcp-remote
      - https://gateway.yahagateway.io/mcp/v1
    env:
      AUTHORIZATION: Bearer yaha.<your-project-key>

Or use HTTP transport per Continue MCP docs. See mcp-tool-bridge.md.

Headless / CI

export OPENAI_API_KEY="yaha.<your-project-key>"
cn -p --config ~/.continue/config.yaml "Summarize this repo"

config.yaml

Agent mode

o-series / GPT-5 models

MCP (Tool Bridge)

Headless / CI

See also

On this page