Checked · 2026-10-20 · Kilo Code 7.8.12 sends gateway traffic to ai-gateway.kilo.ai by default

Kilo Code 7.8.12: gateway traffic goes to ai-gateway.kilo.ai

Kilo Code v7.8.12 (published 2026-10-15) moves Kilo Gateway traffic to https://ai-gateway.kilo.ai/api/v1 by default and adds a KILO_AI_GATEWAY_URL environment variable to override the gateway address.

Updated 2026-10-20

Point this tool at the QCode endpoint — one key for Claude, GPT and Chinese models.

#default gateway address changed#the KILO_AI_GATEWAY_URL override variable#only KILO_API_URL set#request scope for a custom provider

The points: default gateway address, the KILO_AI_GATEWAY_URL override, what happens with only KILO_API_URL, QCode fields

default gateway address

what 7.8.12 changed

The official release states that Kilo Gateway traffic (chat, models, embeddings, autocomplete, transcription) now goes through https://ai-gateway.kilo.ai/api/v1 by default, and those are the request types the release names.

the KILO_AI_GATEWAY_URL override variable

the environment variable the release adds

The same release says a KILO_AI_GATEWAY_URL environment variable is supported to override the default gateway address. Keep the variable name exactly as the release writes it.

only KILO_API_URL set

what the release sentence says

What the official sentence means: setting only KILO_API_URL keeps routing gateway traffic through that server. The release does not further explain what KILO_API_URL points to, or what that server is.

QCode fields

filling the Custom provider dialog

Following the QCode docs page Kilo Code integration: extension settings (gear) → Providers tab → scroll to the bottom → Custom provider dialog; in Models you can type a model id such as claude-sonnet-5 by hand. The full field list is in the section Connect QCode in Kilo Code below.

If I set my own Base URL, can requests still go to ai-gateway.kilo.ai?

Since 7.8.12 Kilo Gateway traffic goes to ai-gateway.kilo.ai by default, and the request types the release names are in the first point above. How the Base URL you entered in a custom provider relates to that default routing is in the section on what the release does not state.

The official 7.8.12 release (checked 2026-10-20)

Checked on 2026-10-20 against the official Kilo release: v7.8.12 was published on 2026-10-15, the change is listed under both the VS Code and the CLI entries, and it is about the default routing of gateway traffic and the environment variable that overrides it, change number #15030. The same release also lists changes for 7.8.10 and 7.8.9, which have nothing to do with gateway routing.

versions and dates

2026-09-18

The QCode docs page Kilo Code integration is marked as last checked on 2026-09-18, against the Kilo Code official documentation.

2026-10-15

Kilo Code v7.8.12 is published: gateway traffic goes to ai-gateway.kilo.ai by default, and the release adds the KILO_AI_GATEWAY_URL environment variable.

2026-10-20

In the full official Kilo release, the only entry about the gateway is the 7.8.12 one.

What the official release states and what it leaves out

Confirmed (checkable in the official release)

① Kilo Gateway traffic (chat, models, embeddings, autocomplete, transcription) goes through https://ai-gateway.kilo.ai/api/v1 by default; ② a KILO_AI_GATEWAY_URL environment variable is added to override the default gateway address; ③ setting only KILO_API_URL keeps routing gateway traffic through that server; ④ the change is listed under both the VS Code and the CLI entries of 7.8.12, change number #15030; ⑤ the release records the publication date 2026-10-15.

What the official release does not state

The release does not say which requests count as Kilo Gateway traffic and which requests go to the Base URL you entered in a custom provider; it also does not say which one wins when KILO_AI_GATEWAY_URL and KILO_API_URL are both set. Both points can only be confirmed by testing in your own environment.

The Kilo official gateway address and the address you enter in a custom provider

what the release states: gateway traffic

The release states that gateway traffic goes to ai-gateway.kilo.ai by default, and lists the change under both the VS Code and the CLI entries of 7.8.12, change number #15030.

what the release does not state: a custom provider

The release does not mention a custom provider or a Base URL, so it does not state how they relate to Kilo Gateway traffic; to see where a request actually goes you have to look in your own environment.

How to check what this change touches for you

① Check the version: confirm your Kilo Code is 7.8.12. ② Check the environment variables: see whether KILO_AI_GATEWAY_URL has been set; when it is not set, the default address the release writes is ai-gateway.kilo.ai. ③ If only KILO_API_URL is set: note that address first and decide afterwards whether to change anything; the release does not say what KILO_API_URL points to. ④ To change the gateway address: point KILO_AI_GATEWAY_URL at an address. ⑤ If you use a custom provider: the fields are in the next section, Connect QCode in Kilo Code. ⑥ Check in a place where you can see where requests go (for example the logs on the side of your own endpoint) which side they land on.

Connect QCode in Kilo Code

Following the QCode docs page Kilo Code integration (updated 2026-10-15): in the VS Code extension open the Kilo Code sidebar settings (gear icon), go to the Providers tab, scroll to the bottom, click Custom provider and fill the dialog field by field. For Claude pick Provider API = Anthropic Messages, put https://api.qcode.cc/api in Base URL and the key starting with cr_ in API key; for GPT models and Chinese models pick OpenAI Compatible, put https://api.qcode.cc/openai/v1 in Base URL and type gpt-6-sol in Models. The docs also say not to use OpenAI Compatible for Claude, because the endpoint returns model_not_available_on_endpoint, and that the Base URL should not end with a slash. On the QCode side you are billed per token, per-model rates are on /models.

Frequently asked questions

What exactly did Kilo Code 7.8.12 change?

The default gateway address. The 7.8.12 release states that Kilo Gateway traffic goes to ai-gateway.kilo.ai by default, and that the KILO_AI_GATEWAY_URL environment variable is added.

What happens if I set only KILO_API_URL?

The release has one sentence on this: setting only KILO_API_URL keeps routing gateway traffic through that server. It does not say which server that is. The variable that overrides the default gateway address is KILO_AI_GATEWAY_URL.

Does this change affect me if I connect my own endpoint through a custom provider?

The official release does not say whether this affects you. The release only writes that Kilo Gateway traffic (chat, models, embeddings, autocomplete, transcription) goes to the new gateway address by default, and it does not mention a custom provider. To see where your own requests go you can only test in your own environment: send one message, then compare what your Base URL side and the ai-gateway.kilo.ai side each received.

How do I fill in the QCode configuration in Kilo Code?

Follow the QCode docs page Kilo Code integration: in the VS Code extension go to the Providers tab, scroll to the bottom and click Custom provider. For Claude pick Anthropic Messages, put https://api.qcode.cc/api in Base URL and the key starting with cr_ in API key; for GPT and Chinese models pick OpenAI Compatible and put https://api.qcode.cc/openai/v1 in Base URL. Do not add a trailing slash to the Base URL.

Can I call Claude through the OpenAI Compatible endpoint?

No. The QCode docs say not to use OpenAI Compatible for Claude, the endpoint returns model_not_available_on_endpoint, and Claude can only go through Anthropic Messages.

How do I get started?

Take your QCode API key in the dashboard, fill in the Custom provider as shown in the section Connect QCode in Kilo Code, and send one message in the chat box to check the connection. On the QCode side you are billed per token, and per-model rates are on /models.

Sources

Official wording: the Kilo official GitHub release v7.8.12 (published 2026-10-15, fetched and checked 2026-10-20), both the release page and the GitHub API response (https://api.github.com/repos/Kilo-Org/kilocode/releases/tags/v7.8.12). On the QCode side: the pages Kilo Code integration and Endpoints and API paths on docs.qcode.cc (fetched and checked 2026-10-20), and the Pay-as-you-go Packs page on qcode.cc (fetched and checked 2026-10-20).

Keep running Kilo Code with a QCode key

Not ready for a monthly plan? Pay-as-you-go Packs start at $4 for a one-time quota you use within 7 to 90 days.

Not sure where to start?

Try it for a week

Week Pack: $4 for $30 of quota, valid 7 days

Use it every day

Starter: $8.57/month, about half the price per $1 of quota compared with the Month Pack ($5 of quota per day)