Skip to main content
Arbytra connects to Kilo Code as a provider, giving you access to multiple models through a single API key.

Prerequisites

  • Kilo Code VS Code extension or CLI
  • An Arbytra API key — your key starts with ak_live_ (production) or ak_test_ (testing)

Install Kilo Code

Open Extensions in VS Code (Cmd+Shift+X on macOS, Ctrl+Shift+X on Windows/Linux), search “Kilo Code”, and install.
Install via npm:
Or via Homebrew (macOS):
Confirm the installation:

Set your API key

Export your API key in your shell:
To persist across sessions, add the same line to ~/.zshrc or ~/.bashrc, then either run source ~/.zshrc (or source ~/.bashrc) or open a new terminal.
Non-interactive shells (CI, Codespaces bash -c, scripts) don’t source ~/.bashrc. For those, export ARBYTRA_API_KEY directly in the environment or source the file explicitly at the top of your script.

Sanity-check the key

Confirm the key works before installing anything else:
Expected: 200. If you get 401, the key is missing, mistyped, or revoked.

Add Arbytra as a provider

VS Code

  1. Open Kilo Code settings (gear icon in the Kilo Code panel).
  2. Go to the Providers tab.
  3. Click Custom provider.
  4. Fill in:
    • Provider ID: arbytra
    • Display name: Arbytra
    • Base URL: https://api.arbytra.com/v1
    • API key: your ak_live_... key
  5. Models auto-populate. Select a model.
  6. Click Submit.

CLI

No registration step is needed — kilo run resolves any arbytra/<model> ID from your API key. Skip to Verify.
If kilo run --model arbytra/<id> returns “model not found” (rare; usually means Kilo’s registry cache didn’t refresh), define the provider locally in a kilo.json at your project root:
This overrides Kilo’s provider registry with a local definition.

Verify

VS Code: Start a chat in the Kilo Code panel and send a message. You should see a response from the model you selected. CLI:
Expected output: setup-ok.
First run only: Kilo performs a one-time SQLite migration (Performing one time database migration, may take a few minutes...). The first call can take up to a minute. Subsequent calls return in seconds.

Set default model

To avoid passing --model on every run, create a kilo.json at your project root:
Place it at ~/.config/kilo/kilo.json for a global default instead. A project-root config takes precedence. VS Code users set their default model in the model picker (top of the Kilo Code panel).

Use different models

Pass any registered model with the --model flag:
VS Code: switch models in the model picker. These models are available through Arbytra:

Known model quirks on Kilo

  • gemini-2.5-flash on tool-call prompts: returns an empty response (no tool invocation, no text). Use gemini-2.5-pro or gemini-3.1-pro-preview for tool-calling workflows on the Gemini family.
  • gemini-2.5-pro on arithmetic: can produce wrong answers when asked for an exact number without showing work. Prompt it to use a tool or show its reasoning for math-critical tasks.
To list every model available on your key (not only the 15 above):

Add unregistered models (advanced)

If you need a model that isn’t in the 15 above and arbytra/<id> doesn’t resolve, define it locally in kilo.json:
Browse model capabilities via the directory API to fill in the model definition fields. VS Code custom provider auto-fetches all models from the API, so this section applies to CLI users only.

Control routing

Configure routing in the Arbytra dashboard. See routing options for details.

Uninstall

VS Code: Remove the Arbytra custom provider from Settings > Providers. Uninstall the Kilo Code extension. CLI: Remove ARBYTRA_API_KEY from your shell profile (~/.zshrc or ~/.bashrc). If you created a kilo.json, remove the arbytra-related lines or delete the file.

Troubleshoot