WorkBuddy Integration

When to Use

WorkBuddy supports configuring custom models. You can integrate Tokener CA as an OpenAI-compatible model provider so WorkBuddy can use platform models for code understanding, editing, explanation, and Agent tasks.

You only need four values to integrate:

Option 1: Configure in the WorkBuddy UI

If your version of WorkBuddy offers a "custom model" or "custom provider" UI, we recommend using it first.

Fill in the values below:

After saving, restart WorkBuddy or refresh the model list, then select the model you just added in the model picker.

Option 2: Use a Local Configuration File

If your version supports local JSON configuration, you can add a Tokener CA model at the user level or project level.

Common configuration locations:

Some WorkBuddy versions reuse the CodeBuddy configuration directory. If .workbuddy doesn't take effect, check for a sibling .codebuddy/models.json, or a .codebuddy/models.json in your user directory.

Example configuration:

{  "models": [    {      "id": "glm-5.3:flash",      "name": "Tokener CA GLM 5.3 Flash",      "vendor": "Tokener CA",      "url": "https://a.tokener.ca/v1/chat/completions",      "apiKey": "${TOKENER_API_KEY}",      "maxInputTokens": 1048576,      "maxOutputTokens": 1048576,      "supportsToolCall": true,      "supportsImages": true    }  ],  "availableModels": [    "glm-5.3:flash"  ]}

The limits shown are the featured model's; for another model, take its context window and max output from its page on /models.

supportsImages above matches the model in the sample. For another model, set it to true only if its page on /models lists image input; otherwise false.

Set Environment Variables

We recommend putting the API Key in an environment variable and having the configuration file only reference the variable.

Current PowerShell window:

$env:TOKENER_API_KEY="tok-..."

Persist on Windows:

setx TOKENER_API_KEY "tok-..."

macOS / Linux:

export TOKENER_API_KEY="tok-..."

After setting it, reopen WorkBuddy to make sure it can read the new environment variable.

Verify the API

Before integrating with WorkBuddy, run a request with the same key and model to make sure it works:

curl -X POST "https://a.tokener.ca/v1/chat/completions" \  -H "Authorization: Bearer <consumer_api_key>" \  -H "Content-Type: application/json" \  --data-raw '{    "model": "glm-5.3:flash",    "messages": [      {        "role": "user",        "content": "Return a short message confirming the integration works."      }    ],    "max_tokens": 64,    "stream": false  }'

If curl succeeds but WorkBuddy can't make the call, first check that WorkBuddy has the full endpoint filled in, not just https://a.tokener.ca/v1.

Troubleshooting Checklist