mirror of https://github.com/Kilo-Org/kilocode.git synced 2026-08-28 19:11:03 +08:00

Files

T

kiloconnect[bot] 06cd80d1bd chore: enforce minimal markdown table formatting

Prettier pads markdown table cells for column alignment, which turns any
content change into a table-wide realignment diff. Markdown was only in
prettierignore for packages/kilo-vscode/; the root formatter still
repadded docs elsewhere (e.g. TESTING.md, kilo-docs, AGENTS.md).

Adds *.md to the root .prettierignore, documents the convention in
AGENTS.md, and adds script/check-md-table-padding.ts + a workflow to
enforce it. Existing padded tables in Kilo-owned docs have been
rewritten via the script's --fix mode.

2026-04-28 07:45:49 +00:00

2.6 KiB

Raw Blame History

title, description

title	description
Bring Your Own Key (BYOK)	Use your own API keys with Kilo Gateway while retaining platform features

Bring Your Own Key (BYOK)

Bring Your Own Key (BYOK) lets you use your own API keys when using the Kilo Gateway, while retaining Kilo platform features like Code Reviews and Cloud Agents.

A user or organization may want to use BYOK to:

Utilize new models quickly, Kilo Gateway supports most new models in minutes
Use subscriptions with third-party AI providers, for example Z.AI or Minimax
Attribute usage against existing provider commitments or agreements
Use existing credits with a provider

Supported BYOK providers

Kilo Gateway currently supports BYOK keys for these providers:

Anthropic
AWS Bedrock
Google AI Studio
Inception
Minimax
Mistral AI
OpenAI
xAI
Z.AI

Add a BYOK key

Log into the Kilo platform and select the account or organization you want to add the BYOK key to.
Navigate to the Bring Your Own Key (BYOK) page, available in the sidebar under Account.
Click Add Your First Key, select the provider, and paste your API key.
Save.

AWS Bedrock configuration

AWS Bedrock requires credentials in a different format than other providers. Instead of a single API key, you must provide your AWS credentials as a JSON object:

{
  "accessKeyId": "AKIA...",
  "secretAccessKey": "...",
  "region": "us-east-1"
}

Field	Description
`accessKeyId`	Your AWS access key ID
`secretAccessKey`	Your AWS secret access key
`region`	The AWS region where Bedrock is enabled (e.g., `us-east-1`, `eu-west-1`)

Your IAM user or role must have the following permissions:

bedrock:InvokeModel
bedrock:InvokeModelWithResponseStream

How Bring Your Own Key works

When you use the Kilo Gateway provider, Kilo checks if there's a BYOK key for the selected model's provider.
If a matching BYOK key exists, the request is routed using your key.
If the key is invalid, the request fails. It does not fall back to using Kilo's keys.

Using BYOK in the Extensions and CLI

BYOK works with the Kilo Gateway provider. Users should ensure that is set as the active provider.
Select a model from a provider configured for BYOK, for example Claude Sonnet 4.5 if you configured BYOK for Anthropic.
(Optional) Validate with the provider that traffic is being served by that key.

Limitations

BYOK is not fully supported by Agent Manager. See Agent Manager for details.

2.6 KiB Raw Blame History