Editor Extensions

Continue

Configure an OpenAI provider in local YAML for chat and editing.

ConfigurableOpenAI Chat CompletionsDocs checked 2026-09-18

The vendor documents custom endpoints. Check model capabilities and verify the connection.

On this page

Before you begin

Install the official Continue extension. This uses the current YAML format; migrate legacy config.json using the official guide.

Have an A2Agent API key ready and copy an accessible model ID from the catalog. Replace every placeholder, back up existing settings and keep keys out of repositories.

Manage API keys Browse models

Setup

File contents are usually shared; switching OS changes commands and paths. For WSL on Windows, select macOS / Linux.

01Open local configuration
Open local configuration from Continue’s configuration selector and make a backup.
Open official documentation

02Add a model

Merge the models array and replace the placeholders. apiBase includes /v1 but not /chat/completions. This local file contains a key; keep it out of the repository.

~/.continue/config.yaml

name: A2Agent
version: 1.0.0
schema: v1
models:
  - name: A2Agent
    provider: openai
    model: YOUR_MODEL_ID
    apiBase: "https://a2agent.me/v1"
    apiKey: "YOUR_A2AGENT_API_KEY"
    useResponsesApi: false

03Select the configuration and model
After saving, select the local configuration and A2Agent model in Continue, then start a new chat.

Capabilities and limits

Autocomplete needs a suitable completion model, and indexing needs embeddings. This chat configuration does not configure either.
Agent tool use depends on the model and its capability settings.

Verify the connection

Replace every placeholder and run locally. Expect JSON containing OK. Then start a new client conversation, test one read-only tool call separately, and confirm the requests in A2Agent usage records. This test incurs a small amount of model usage.

Shell

curl --fail-with-body --silent --show-error --max-time 60 'https://a2agent.me/v1/chat/completions' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_A2AGENT_API_KEY' \
  -d '{"model":"YOUR_MODEL_ID","max_tokens":128,"messages":[{"role":"user","content":"Reply with OK."}]}'

Troubleshooting

For loading errors, check YAML indentation and schema. If requests still use the official endpoint, select the local configuration.

401 / 403: authentication or access denied

Use a key issued by A2Agent, without extra spaces, and check that it is active and unexpired. Confirm the group permits the model and protocol. A vendor subscription credential cannot replace an A2Agent key.

404 / model not found: endpoint or model mismatch

Check the root URL, /v1 prefix and full request path against this guide; avoid duplicated paths. Model IDs are case-sensitive and must be accessible to the current key.

429: quota or rate limit

Check your balance, key limits, concurrent usage and service status. Wait before retrying and reduce simultaneous agents; repeated retries do not remove a quota limit.

Chat works, but tools fail or streaming stops

Test a short text request, then a single read-file tool call. Check tool support, output budget, proxy timeouts and client version. Inspect the diff before resuming a long task to avoid repeating actions.

Restore previous settings

Switch to the previous configuration, remove the added model and key, or restore the backup.

Sources and check date

Status is based on official configuration docs, not end-to-end client testing with A2Agent.

Docs checked 2026-09-18