AI Tool Setup
Yokai discovers running inference services, exposes their tunneled endpoints, and can write supported client configurations from the Settings route.
Supported clients
Section titled “Supported clients”| Client | Integration behavior |
|---|---|
| VS Code Copilot | Adds OpenAI-compatible entries under chat.models[] |
| OpenCode | Adds one provider per host through @ai-sdk/openai-compatible |
| OpenClaw | Adds a Yokai provider under models.providers |
| Claude Code | Sets ANTHROPIC_BASE_URL, ANTHROPIC_MODEL, and ANTHROPIC_CUSTOM_MODEL_OPTION |
| Codex | Adds a Yokai provider under [model_providers.yokai] |
Configure from Settings
Section titled “Configure from Settings”- Ensure at least one compatible inference service is running.
- Open Settings with
4. - Toggle clients with
V(VS Code),O(OpenCode),L(OpenClaw),K(Claude Code), orX(Codex). - Press
Cto configure the selected clients.
The daemon detects each expected configuration path and reports whether the tool is available and already configured.
Backup behavior
Section titled “Backup behavior”Before modifying an existing file, an integration writer creates a sibling .yokai.bak. Review or restore the backup if you want to remove the generated endpoints.
Endpoint discovery
Section titled “Endpoint discovery”The daemon exposes normalized OpenAI-compatible endpoints at:
GET http://127.0.0.1:7473/integrations/openai-endpointsEach endpoint includes the service, device, model, and local tunneled URL. This is also useful for unsupported clients.
Manual configuration
Section titled “Manual configuration”Use the local tunneled endpoint shown by Yokai:
export OPENAI_BASE_URL="http://127.0.0.1:<local-port>/v1"export OPENAI_API_KEY="not-needed"Use the exact model ID reported by the running service. If the backend enforces its own API key, use that value instead.
Client notes
Section titled “Client notes”Claude Code
Section titled “Claude Code”Claude Code expects an Anthropic-style configuration. Yokai writes the custom base URL and model fields supported by Claude Code. Confirm that the selected backend provides the compatibility behavior your workflow needs.
Yokai adds a named provider rather than replacing unrelated providers. Select the corresponding provider and model in your Codex configuration or session.
Multiple endpoints
Section titled “Multiple endpoints”Yokai can register every eligible running endpoint. Client UIs decide how the entries are selected; Yokai does not proxy or load-balance requests between them.
Remove generated configuration
Section titled “Remove generated configuration”Restore the .yokai.bak file or remove only the generated Yokai provider/model entries. Restart the client so it reloads configuration.