workbuddy-cli-model-bridge

The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.

---
name: workbuddy-cli-model-bridge
description: Install, audit, repair, and manage a loopback-only CLIProxyAPI
  bridge that registers subscription-backed Codex, Grok, Antigravity/Gemini,
  GLM Coding Plan, or newly added CLI models in WorkBuddy. Use whenever the
  user asks to connect a local CLI or agent model to WorkBuddy, install
  CLIProxyAPI, add GLM-5.3 from a Coding Plan key, add or repair a WorkBuddy
  custom model, preserve image/tool/reasoning/Fast capabilities, onboard
  another CLI provider, or diagnose a WorkBuddy model that stopped working.
  This Skill is macOS-first and should be used even when the user names only
  the model or says their local WorkBuddy API has expired.
disable-model-invocation: true
---

# WorkBuddy CLI Model Bridge

Turn supported CLI subscriptions into verified WorkBuddy custom-model entries through CLIProxyAPI. Use the bundled script for discovery, installation, OAuth handoff, capability probes, and idempotent WorkBuddy updates. Keep model claims tied to real probes; a model name or marketing page is not evidence that a particular proxy route preserves the capability.

## Resolve the Skill directory

Resolve this loaded Skill's directory and use its absolute path as `<skill-dir>`. Do not assume a specific installation root.

The deterministic entry point is:

```bash
python3 <skill-dir>/scripts/bridge.py
```

## Default workflow

### 1. Audit before changing anything

```bash
python3 <skill-dir>/scripts/bridge.py audit
```

Read the JSON findings. The audit redacts secrets and detects:

- Homebrew, CLIProxyAPI, active config, bind address, and proxy reachability
- WorkBuddy initialization and existing model count
- bundled and local Provider manifests
- CLI executables and login signals without reading token contents
- CLIProxyAPI auth-file counts without exposing account names

Treat an existing CLI login as a discovery signal. CLIProxyAPI may still require its own OAuth grant; do not copy another CLI's token file.

### 2. Bootstrap CLIProxyAPI when required

Preview:

```bash
python3 <skill-dir>/scripts/bridge.py bootstrap
```

Apply the plan when the user asked to install, configure, repair, or converge the bridge:

```bash
python3 <skill-dir>/scripts/bridge.py bootstrap --apply
```

The request to set up the bridge authorizes reversible Homebrew installation, loopback service startup, a dedicated random proxy client key, secure local state, and timestamped backups. Pause only when:

- Homebrew itself is missing and its installer requires administrator interaction
- an existing proxy listens beyond loopback; explain the remote-client impact before using `--allow-rebind-local`
- an overlapping deployment or config conflict makes ownership ambiguous

Keep a healthy existing installation in place. Prefer official Homebrew installation for a new macOS setup.

### 3. Authorize only relevant Providers

Bundled OAuth Provider IDs are `codex`, `xai-grok`, and `antigravity`. Authorize one when the user requested it or the audit found its CLI/login signal and CLIProxyAPI has no matching auth/model route.

```bash
python3 <skill-dir>/scripts/bridge.py authorize codex
python3 <skill-dir>/scripts/bridge.py authorize xai-grok
python3 <skill-dir>/scripts/bridge.py authorize antigravity
```

The command delegates to CLIProxyAPI's native OAuth flag. Tell the user to approve the browser page, then continue automatically. Never paste, print, transform, or reuse OAuth tokens. Secure resulting auth JSON files to owner-only permissions.

Bundled `glm-coding` is a Coding Plan API-key Provider, not OAuth. Do not run `authorize glm-coding`. Follow [glm-coding-plan.md](references/glm-coding-plan.md): add the official coding `/paas/v4` route to CLIProxyAPI, then `sync --providers glm-coding`. Do not use 智谱清言 website login.

Do not authorize unrelated Providers merely because they are bundled.

### 4. Probe and synchronize WorkBuddy

Pass only the relevant Provider IDs:

```bash
python3 <skill-dir>/scripts/bri