Skip to main content
Use Custom Models to connect an endpoint you operate or obtain from a hosted service. You supply its address and exact model identifier, then choose the saved model from the composer in Zen mode. For built-in integrations such as OpenAI, Anthropic, or Google, start with Connect providers.

Before you start

Have these details ready:
  • An OpenAI-compatible API base URL reachable from the computer running Kisuke Connect.
  • The exact model ID accepted by that endpoint.
  • An API key or additional request headers, if the endpoint requires them.
Start the model server before testing. A custom model definition belongs to one Connect device; it does not automatically synchronize to your other devices. An address using localhost refers to the computer running Connect, which may be different from the device displaying Kisuke.

Add the endpoint

1

Open custom models

Open Settings → Providers, find Custom Models, and choose + Add custom model.
2

Enter the connection details

Enter a Name, Base URL, and Model ID. Add the API key if required. Expand Advanced — custom headers for any extra headers required by your gateway.
3

Test before saving

Select Test connection. Review the result and any reply sample. Testing uses the current form values and does not save the definition.
4

Save and select

Choose Add model, then open a new conversation’s model picker. Look for your saved name under Custom in a harness that exposes custom models.

Understand the fields

For example, a base URL of http://localhost:11434/v1 makes the connection test call http://localhost:11434/v1/chat/completions. This illustrates the URL format; it does not install a server or download a model.

What the connection test proves

Test connection sends a small, non-streaming request containing ping, your model ID, and a one-token output limit. It then tries to read the endpoint’s advertised model list. Connected means the completion request returned a successful HTTP status. Kisuke may also display a reply sample and the number of models advertised by the endpoint. The advertised list is optional; failure to retrieve it does not make the completion check fail.
A successful test does not validate the full response format. An endpoint can return a successful HTTP status without a usable model reply. It also does not verify streaming, tool use, image input, or a complete agent turn.
After saving, try a small request in a new conversation and verify the actual response. Check the endpoint’s capabilities against the tools and input types you intend to use. Do not assume that every endpoint or harness supports the same features.

Edit or remove a definition

In Settings → Providers → Custom Models, choose Edit beside a model. Update the fields, test the edited values, and choose Save. Cancel closes the form without saving. Choose Delete, then Confirm, to remove the saved definition from that Connect device. This removes Kisuke’s connection entry; it does not uninstall your model server. Choose Cancel at the confirmation prompt to retain it.

Resolve connection problems

If the composer rejects a first message before the endpoint receives it, see Troubleshoot a first message.