OpenCode CLIProxyAPI

Fork of opencode-cliproxyapi that uses every model exposed by CLIProxyAPI directly in OpenCode. This fork adds automatic reasoning-effort configuration queried from the CLIProxyAPI server itself.

The plugin discovers CLIProxyAPI's live /v1/models catalog whenever OpenCode starts. Available models appear in the normal /models picker under CLIProxyAPI. OpenCode Go models that expose Anthropic-compatible endpoints are automatically routed through /v1/messages using live model metadata from models.dev; the remaining discovered models continue to use the provider's configured default protocol. No model IDs are hard-coded.

For every model whose reasoning levels are known to the CLIProxyAPI server itself, the plugin also:

• marks the model as a reasoning model,
• sets the server-reported default reasoning effort as the model default, and
• registers each supported effort (low, medium, high, …) as a model variant you can cycle with the variant keybind.

Effort levels are taken from CLIProxyAPI's codex-client catalog (the same data its Codex clients use), so models that the server cannot describe keep the plugin's previous id-based heuristics.

You need OpenCode, a running CLIProxyAPI server, and one of its API keys.

The plugin is published as @darknesskiller/opencode-cliproxyapi. OpenCode installs npm plugins automatically when it starts, so listing the package in your config (next step) is enough — no manual download or build.

Open your global OpenCode config:

~/.config/opencode/opencode.json

Create it if it does not exist; either opencode.json or opencode.jsonc works. Configure the plugin entry with the npm package name, plus your persistent server URL and API key:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": [
    [
      "@darknesskiller/opencode-cliproxyapi",
      {
        "baseURL": "http://your-server:8317",
        "apiKey": "your-cli-proxy-api-key"
      }
    ]
  ]
}

The first OpenCode start downloads the package; later releases are picked up after OpenCode restarts. Do not install the original opencode-cliproxyapi package at the same time — both register the same cliproxyapi provider.

The URL may include /v1, but it is not required. If baseURL is omitted, the plugin uses http://localhost:8317/v1.

Keep this global config private because it contains your API key. Do not copy the connection into a project's opencode.json or commit it to a repository.

opencode models cliproxyapi

You should see models reported by your server:

cliproxyapi/claude-sonnet-4-6
cliproxyapi/gpt-5.6-terra
cliproxyapi/gemini-3.1-pro-low

Start OpenCode and run /models:

opencode

Choose CLIProxyAPI, select a model, and use OpenCode normally. Restart OpenCode whenever the model catalog on CLIProxyAPI changes.

This release stores the connection in OpenCode's global config instead of using the /connect screen. Model selection itself uses the standard /models experience.

The recommended configuration is the global plugin entry shown above (with the npm package name):

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": [
    [
      "@darknesskiller/opencode-cliproxyapi",
      {
        "baseURL": "http://your-server:8317",
        "apiKey": "your-cli-proxy-api-key",
        "providerName": "My CLIProxyAPI"
      }
    ]
  ]
}

If model metadata cannot be reached, the plugin logs a warning and keeps the CLIProxyAPI-discovered models available with the configured default protocol.

Environment variables remain available for containers, CI, or users who prefer not to place a key in the config:

export CLIPROXY_BASE_URL="http://your-server:8317"
export CLIPROXY_API_KEY="your-cli-proxy-api-key"

Put these lines in your shell profile if you want them to persist. Explicit plugin options in opencode.json take precedence over environment variables.

Existing provider.cliproxyapi settings are preserved, so individual models can be customized:

{
  "provider": {
    "cliproxyapi": {
      "models": {
        "gpt-5.6-terra": {
          "name": "Terra",
          "limit": {
            "context": 200000,
            "output": 65536
          }
        }
      }
    }
  }
}

OpenCode v2 replaced the plugin array with plugins and no longer runs v1 plugin code. This package ships a dual entrypoint: v2 calls setup(ctx) and v1 (1.18.29 and newer) calls server(ctx), so one configuration works on both.

// OpenCode v2 (~/.config/opencode/opencode.jsonc)
{
  "$schema": "https://opencode.ai/config.json",
  "plugins": [
    {
      "package": "@darknesskiller/opencode-cliproxyapi",
      "options": {
        "baseURL": "http://your-server:8317",
        "apiKey": "your-cli-proxy-api-key"
      }
    }
  ]
}

On v2 the plugin registers the provider itself: it publishes the discovered catalog through ctx.provider.transform, selects @opencode/ai/providers/openai-compatible (or @opencode/ai/providers/openai with protocol: "responses"), and routes Anthropic-endpoint models through @opencode/ai/providers/anthropic. Every option in the table above works unchanged inside the plugin entry's options.

To run a checkout instead of the published package, point package at the repository directory (OpenCode resolves its root index.ts) and use the local path:

{
  "plugins": [
    {
      "package": "/path/to/opencode-cliproxyapi",
      "options": { "baseURL": "http://your-server:8317" }
    }
  ]
}

Check that the global plugin entry contains a non-empty apiKey, then restart OpenCode. If you chose environment variables instead, ensure CLIPROXY_API_KEY is available to the process that starts OpenCode.

First check the API directly:

curl -H "Authorization: Bearer your-cli-proxy-api-key" \
  "http://your-server:8317/v1/models"

Then restart OpenCode and run:

opencode models cliproxyapi

Move the connection to the recommended global OpenCode config, or add the environment variables to your shell profile.

Restart OpenCode so it picks up the newest published version of the npm package. If the package was never installed, check that the name in the plugin list is exactly @darknesskiller/opencode-cliproxyapi and that you are not also loading the original opencode-cliproxyapi package (both register the same cliproxyapi provider).

git clone https://github.com/DarknessKiller/opencode-cliproxyapi.git
cd opencode-cliproxyapi
bun install
bun run check

The repository's opencode.json loads the local build for integration testing:

bun run build
export CLIPROXY_BASE_URL="http://your-server:8317"
export CLIPROXY_API_KEY="your-cli-proxy-api-key"
opencode models cliproxyapi

See CONTRIBUTING.md for contribution guidelines and SECURITY.md for private vulnerability reporting.

MIT