Editor Extensions

Kilo Code

Use an OpenAI-compatible endpoint in a Kilo Code profile.

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 Kilo Code from the marketplace linked by its official site and choose a tool-capable model. In remote development, check whether settings apply locally or remotely.

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.

01Install and add a profile
Add an API configuration profile in Kilo Code extension settings and choose OpenAI Compatible.
Open official documentation
02Enter connection details
Enter and save these values, then select the profile for a new task. Put the key in the extension’s credential field, not project settings.
text
```
Base URL: https://a2agent.me/v1
API Key: YOUR_A2AGENT_API_KEY
Model ID: YOUR_MODEL_ID
```

Capabilities and limits

Select OpenAI Compatible to use the custom endpoint. Kilo’s own provider has separate credits and authentication.
Test tool calls, images and long context separately. A text reply alone does not verify all capabilities.

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 a 401, check the key and group. For a missing model, check its ID. If chat works but tools fail, check model tool support and extension capability settings.

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

Return to the previous profile and remove the added profile and key. There is no need to reset the editor.

Sources and check date

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

Docs checked 2026-09-18

Kilo Code · OpenAI Compatible