Skip to main content
Run phaseo kilo to start a Kilo Code CLI session through Phaseo, or create a key with phaseo kilo-code and add a custom provider in the Kilo Code extension.

​
Run the Kilo Code CLI through Phaseo

The runner writes a temporary KILO_CONFIG file, launches kilo, and deletes the file when Kilo exits, so your existing Kilo Code or VS Code setup is untouched. If Kilo is missing, an interactive run offers to install it. Put Kilo’s own flags after --. phaseo run kilo ... is the long form of the same command.

​
Configure the Kilo Code extension

Create a key for the extension:
Then, in VS Code:
  1. Open Kilo Code, select the settings icon, open Providers, then select Add custom provider.
  2. Enter:
  1. If no model is discovered, add the ID anthropic/claude-sonnet-5.5 yourself.
  2. Select Submit, then choose the Phaseo model.
Kilo shows the selection as phaseo/anthropic/claude-sonnet-5.5. phaseo is the local provider ID; the rest is the model ID sent to Phaseo. See Kilo’s custom models docs for the full form.

​
Check it works

Ask Kilo Code to reply with PHASEO_KILO_OK, then confirm the request appears in Settings → Usage → Logs.

​
Remove Phaseo

Delete the custom provider in Kilo Code, then run:
This revokes the key. The CLI can’t clear the extension’s storage.

​
Fix common problems

​
No models are discovered

Add the model yourself. Kilo doesn’t need discovery through /models.

​
Authentication fails

Replace the saved key with the output of phaseo integrations credential kilo-code, and keep the Base URL exactly as shown.

​
The model name looks different

Select phaseo/<Phaseo model ID> in Kilo, but don’t add phaseo/ in the model ID field.
Last modified on November 5, 2026