Developer Integrations

This is the main public guide for BotConnector integrations. Sign-in is only required when creating a BotConnector API key.

Install BCCLI

bash

npm install -g @botconnector/bccli
bccli login bc-cloud

Connect the tool you use:

bash

bccli connect opencode
bccli connect cline
bccli connect aider
bccli connect deepseek-harness
bccli connect codex
bccli connect claude-code
bccli connect cursor
bccli connect openai-cli
bccli connect openai-sdk
bccli connect openai-compatible

Check status or restore configuration:

bash

bccli integrations
bccli disconnect <integration-name>

BCCLI creates backups before changing managed external configuration.

Protocols used

Client	BotConnector protocol
OpenCode / Cline / Aider / DeepSeek Harness	`/v1/chat/completions`
Codex CLI	`/v1/responses`
Claude Code	`/v1/messages` + `/v1/messages/count_tokens`
OpenAI CLI / SDK / compatible clients	OpenAI-compatible profile
Cursor	Guided OpenAI Base URL setup
Kelivo (Android / iPhone)	`/v1/chat/completions`
Crush	`/v1/chat/completions`
Kilo Code	`/v1/chat/completions`

Kelivo

Kelivo is an open-source mobile client that can connect directly to BotConnector's OpenAI-compatible endpoint without requiring a Kelivo account.

Install Kelivo from the App Store or Android releases.
On Providers, tap the + button at the top right and choose Import Provider. Do not select a built-in provider such as OpenAI, Gemini, OpenRouter, or SiliconFlow.
Paste the configuration from the BotConnector Kelivo provider, then tap Import. A new provider named BotConnector will appear.
Other built-in providers may stay ON; you do not need to change them. When using BotConnector, select the BotConnector provider/model.
Open BotConnector → Config and enter your bc_live_... key from Workspace → API Keys.
Under Models, tap Fetch. Kelivo reads your account model list from GET https://api.botconnector.id/v1/models.

The import configuration never contains your API key. For direct chat attachments, Kelivo extracts PDF, DOCX, TXT, Markdown, CSV, JSON, and text/code files locally. Direct extraction is limited to 16 MB per file; use the BotConnector Web App / Workspace for larger files.

Crush Beta

Crush supports BotConnector through its native openai-compat provider type and can discover account-visible models from GET /v1/models.

Create an API key in Workspace → API Keys.
Export it before starting Crush:

bash

export BOTCONNECTOR_API_KEY="bc_live_..."

Add this to ~/.config/crush/crushrc:

bash

provider add botconnector \
  --name "BotConnector" \
  --type openai-compat \
  --base-url "https://api.botconnector.id/v1" \
  --api-key "${BOTCONNECTOR_API_KEY:?set BOTCONNECTOR_API_KEY}" \
  --discover-models true

Crush will merge discovered BotConnector models with any models already configured for that provider. Other Crush providers are unaffected.

Kilo Code Beta

Kilo Code can connect to BotConnector as a custom OpenAI-compatible provider and automatically fetch models from the account.

Open Settings → Providers → Custom provider.
Set:

Provider ID: botconnector
Display name: BotConnector
Provider API: OpenAI Compatible
Base URL: https://api.botconnector.id/v1
API key: your bc_live_... key

Click Fetch models, select the BotConnector models you want, then save.

Kilo Code queries BotConnector's authenticated /v1/models endpoint, so the picker follows the models available to that API key.

OpenCode

bash

bccli connect opencode

BCCLI fetches the model catalog, adds the botconnector provider, preserves other providers, and writes ~/.config/opencode/opencode.json. Then run opencode normally.

Disconnect: bccli disconnect opencode.

Cline

bash

bccli connect cline

BCCLI manages ~/.cline/data/settings/providers.json, configures the openai-compatible provider, the BotConnector Base URL, and an active default model. It will not silently overwrite a different existing OpenAI-compatible endpoint.

Disconnect: bccli disconnect cline.

Aider

bash

bccli connect aider

BCCLI manages ~/.aider.conf.yml and ~/.bccli/integrations/aider.env. Then run aider normally.

Disconnect: bccli disconnect aider.

DeepSeek Harness

1. Connect BotConnector

Run this one command:

bash

bccli connect deepseek-harness

When it succeeds, BCCLI adds the botconnector provider to DeepSeek Harness without removing other DSH providers.

Optional short alias: bccli connect dsh. It does the same thing, so you do not need to run both.

2. Start DeepSeek Harness

After the integration succeeds, run:

bash

dsh web

Do not run dsh by itself: DeepSeek Harness 0.1.x requires a profile and will return --profile <name> is required.

Do not run deepseek-harness: the installed executable is named dsh.

The equivalent long form is:

bash

dsh --profile web

3. Configuration created

BCCLI manages:

$DSH_HOME/settings.yaml
$DSH_HOME/.env

The provider uses api: openai-completions, Base URL https://api.botconnector.id/v1, and BOTCONNECTOR_API_KEY.

4. Disconnect

Use:

bash

bccli disconnect deepseek-harness

The short alias bccli disconnect dsh is also available.

Codex CLI

bash

bccli connect codex

BCCLI creates ~/.codex/botconnector.config.toml with wire_api = "responses" and Base URL https://api.botconnector.id/v1.

BCCLI also creates a launcher:

Linux/macOS: ~/.bccli/integrations/codex-botconnector
Windows: %USERPROFILE%\.bccli\integrations\codex-botconnector.cmd

Run that launcher to use Codex through BotConnector. Disconnect: bccli disconnect codex.

Claude Code

bash

bccli connect claude-code

BCCLI creates a Claude Code launcher with ANTHROPIC_BASE_URL=https://api.botconnector.id, the BotConnector API key, and a BotConnector coding model.

Launcher:

Linux/macOS: ~/.bccli/integrations/claude-botconnector
Windows: %USERPROFILE%\.bccli\integrations\claude-botconnector.cmd

Disconnect: bccli disconnect claude-code.

Cursor

bash

bccli connect cursor

Cursor uses guided setup. BCCLI creates ~/.bccli/integrations/cursor.txt and does not modify undocumented Cursor internal storage.

In Cursor open Settings → Models, add your BotConnector API key, enable Override OpenAI Base URL, and use https://api.botconnector.id/v1.

Important: Cursor's Base URL override applies broadly to OpenAI-family requests. Disable it when switching back to Cursor-managed OpenAI-family models.

OpenAI CLI

bash

bccli connect openai-cli

BCCLI creates a launcher that sets OPENAI_BASE_URL and reads the API key from BCCLI storage instead of embedding it in the script.

Launcher: ~/.bccli/integrations/openai-botconnector or openai-botconnector.cmd on Windows.

OpenAI SDK

bash

bccli connect openai-sdk

BCCLI creates ~/.bccli/integrations/openai-sdk.env containing OPENAI_BASE_URL=https://api.botconnector.id/v1 and the API key. Load that env file into your Python/Node application and use the OpenAI SDK normally.

OpenAI-compatible

bash

bccli connect openai-compatible

BCCLI creates ~/.bccli/integrations/openai-compatible.env. Use that profile with any client that supports a custom OpenAI Base URL.

API keys and security

Create an API key from Workspace → API Keys. Reading this page does not require login.

External agents call BotConnector directly and do not automatically inherit access reserved specifically for the BotConnector Web App or BCCLI.

Troubleshooting

bash

bccli integrations
bccli disconnect <integration-name>

If models are stale, run bccli connect ... again so BCCLI refreshes the BotConnector model catalog.