Kilo Code
Operating the Kilo Code CLI on workers — sign-in, `kilo run`, provider names, and add-on models through KILO_CONFIG_CONTENT.
Install
npm install -g @kilocode/cliThe worker looks for kilo on the worker user's PATH.
Sign-in
Run kilo auth once as the worker's user. Without a login a run ends with "You need to sign in to use this
model".
How it runs
kilo run --format json --auto [-m <provider>/<model>] <message>
- Kilo Code is built on OpenCode and keeps its command line and JSON events, so the worker reuses that adapter.
--autoapproves permissions that are not explicitly denied.- Provider names are OpenCode's:
azure,amazon-bedrock,google-vertex. - The worker also finds it under the name
kilocode.
Add-on models
The worker passes a KILO_CONFIG_CONTENT that points Kilo Code at the model gateway. A complete task was run
this way against a test model. Ollama and OpenAI-compatible providers reach it this way too, because Kilo Code
has no provider for an arbitrary endpoint.
Sessions
Resume is not claimed for Kilo Code: no resume command could be verified without an account. After a crash, recovery starts a fresh session from the checkpoint.
What was verified
Checked against Kilo Code 7.8.3 on 2026-10-06: its --help, and a real run without credentials through the
worker's session runtime. It also completed a task through the model gateway against a test model.