Cline, Roo, Kilo
Cline, Roo, Kilo
These extensions all speak the OpenAI chat protocol, so one configuration shape covers
all of them. Only the settings screen differs.
The four values you need
| Field | Value |
|---|---|
| Provider / API type | OpenAI Compatible |
| Base URL | https://hisoka.ai/api/v1 |
| API key | your sk-... key |
| Model ID | any id from GET /models |
Cline
- Open the Cline panel, then the settings gear.
- API Provider:
OpenAI Compatible. - Base URL:
https://hisoka.ai/api/v1. - API Key: paste your key.
- Model ID: type the exact id, for example
glm-5.3-flash.
Cline may not offer a dropdown here, because it lists models from its own catalogue. Typed
ids work; that is not a fallback, it is the documented path for a compatible provider.
Roo Code
Same screen, same values. Roo additionally lets you preload a model list, which is useful
because Hisoka’s catalogue changes as models are added.
Kilo Code
Identical to Cline. Provider OpenAI Compatible, then the base URL, key and model id.
Continue
Continue uses a config file:
models:
- name: Hisoka GLM
provider: openai
model: glm-5.3-flash
apiBase: https://hisoka.ai/api/v1
apiKey: sk-your-key-here
aider
export OPENAI_API_BASE="https://hisoka.ai/api/v1"
export OPENAI_API_KEY="sk-your-key-here"
aider --model openai/glm-5.3-flash
aider needs the openai/ prefix in the model name to route through the OpenAI-compatible
path; the part after the slash is the Hisoka model id.
Pick one whose capabilities.tools is true and whose context_window is large enough for
the repository you are working in. Both fields are on every /models row, so you can
decide before starting a session instead of discovering it mid-task.
If tool calls misbehave
The gateway never rewrites a tool_choice you left unspecified. If an agent loops on the
same tool, the cause is usually a client forcing tool_choice: required, which forbids
the model from answering without a tool call. Check the client setting before the gateway.