Skip to content

Configure Tencent WorkBuddy

Updated: 2026-08-20

This page provides a screenshot-based walkthrough for connecting Tencent WorkBuddy to the Cubicspaces OpenAI-compatible API.

Before you begin, obtain the following from the Cubicspaces console:

  • An API Key
  • A model ID available to your account, such as gpt-5.6-sol

WorkBuddy uses the OpenAI Chat Completions protocol. Do not configure the endpoint as /v1/responses.

The UI screenshots on this page are from the official Tencent Cloud WorkBuddy documentation. Colors and layout may differ slightly between versions, but the fields are equivalent. No Cubicspaces API Key appears in the screenshots.


Supported Model IDs

Replace the example model with a model available to your account. If the console shows only some of these models for your account, use the model IDs actually available there.

GPT

For WorkBuddy, prefer these GPT model IDs that support tool calling:

  • gpt-5.6-sol
  • gpt-5.6-luna
  • gpt-5.6-terra
  • gpt-5.5
  • gpt-5.4
  • gpt-5.4-mini

These models use the same Provider, Endpoint, API Key, and Custom Protocol settings; only the model ID changes. gpt-5.6-sol is the recommended default.

Other GPT models compatible with the OpenAI Chat Completions protocol use the same configuration. Replace only the model ID with a name available in the Cubicspaces console.

Claude

Claude models also connect to WorkBuddy through the OpenAI Chat Completions protocol:

  • claude-sonnet-5
  • claude-sonnet-4-6
  • claude-opus-5
  • claude-opus-4-8
  • claude-opus-4-7
  • claude-opus-4-6
  • claude-haiku-4-5
  • claude-fable-5

These Claude models use the same setup; only the model ID changes. WorkBuddy automatically sends the conversation as the messages field in the request body, so you do not need to add messages manually.

Configure image input, reasoning mode, tool calling, and token limits according to the capabilities of the selected model. A model without tool-calling support cannot provide the full WorkBuddy coding-agent experience.


Step 1: Open WorkBuddy Settings

  1. Start WorkBuddy.
  2. Select the account or avatar in the lower-left corner.
  3. Select Settings.

Open WorkBuddy settings


Step 2: Open Model Configuration

  1. Select Model in the settings sidebar.
  2. Under Custom Models, select Add Model.

Open model settings and add a model

Current WorkBuddy versions manage the local configuration through the UI. You do not need to edit JSON first.


Step 3: Select the Custom Provider

Open the provider list and select Custom at the bottom.

Select the Custom provider


Step 4: Enter the Cubicspaces Settings

Enter the following values:

SettingValue
ProviderCustom
Endpointhttps://cubicspaces.cloud/v1
API KeyThe API Key created in the Cubicspaces console
Modelgpt-5.6-sol, or another model ID shown in the console
Tool callingEnabled
Image inputEnable when needed; GPT-5.6 supports it
Reasoning modeEnabled
Custom ProtocolDisabled
Input limit128K
Output limit16K

Enter the custom model settings

In standard mode, keep Custom Protocol disabled. WorkBuddy appends /chat/completions to https://cubicspaces.cloud/v1.

If an exact endpoint is required:

  1. Enter https://cubicspaces.cloud/v1/chat/completions as the endpoint.
  2. Enable Custom Protocol.

Use one mode or the other. Do not create a duplicated path such as:

text
/v1/chat/completions/chat/completions

Step 5: Save and Select the Model

  1. Confirm that the API Key contains no extra spaces or quotation marks.
  2. Select Save.
  3. Return to the chat page and select the model name below the input box.
  4. Select gpt-5.6-sol from the Custom Models group.

Select the custom model in chat


Step 6: Verify Tool Calling

With a workspace open, send:

text
List the files in the current workspace and summarize the project structure.

If WorkBuddy can inspect the workspace and return a result, the model and tool calling are connected.

WorkBuddy should continue to use /v1/chat/completions. When GPT-5.5 or GPT-5.6 is used with tool calling and reasoning, Cubicspaces handles protocol compatibility on the server; you do not need to change WorkBuddy to /v1/responses.


Fallback: models.json

The UI is the recommended setup method; editing JSON is not required. WorkBuddy 5.3.13 stores its user-level configuration at:

text
~/.workbuddy/models.json

Windows path:

text
%USERPROFILE%\.workbuddy\models.json

Single-model example for WorkBuddy 5.3.13:

json
{
  "id": "gpt-5.6-sol",
  "name": "gpt-5.6-sol",
  "vendor": "Custom",
  "url": "https://cubicspaces.cloud/v1",
  "apiKey": "YOUR_API_KEY",
  "maxInputTokens": 128000,
  "maxOutputTokens": 16384,
  "supportsToolCall": true,
  "supportsImages": true,
  "supportsReasoning": true,
  "useCustomProtocol": false
}

Older CodeBuddy or pre-migration WorkBuddy versions may use ~/.codebuddy/models.json, and current versions may continue to read legacy settings. JSON structures can differ between versions, so prefer Settings → Model and do not maintain both directories at the same time.

Claude Model Setup

Claude models are also added as Custom Models in WorkBuddy. Use the same Provider, Endpoint, API Key, and Custom Protocol settings as the GPT models. Set the model name to a model ID from the Claude list above, such as claude-sonnet-5.

SettingValue
ProviderCustom
Endpointhttps://cubicspaces.cloud/v1
API KeyThe API Key created in the Cubicspaces console
ModelFor example, claude-sonnet-5, or another supported Claude model ID below
Tool callingEnabled
Image inputEnable when needed; follow the selected model's capabilities
Reasoning modeIf the model reports an unsupported parameter, disable it and retry
Custom ProtocolDisabled

WorkBuddy still connects to Claude models through the OpenAI Chat Completions protocol. Do not change the endpoint to Claude's native /v1/messages.

WorkBuddy automatically sends the conversation as the messages field in the Chat Completions request body. You do not need to add a messages field manually in the WorkBuddy model settings or models.json.


Troubleshooting

HTTP 404 or a duplicated path

In standard mode, use https://cubicspaces.cloud/v1 and disable Custom Protocol. When using the complete /v1/chat/completions endpoint, enable Custom Protocol.

HTTP 401

Confirm that the API Key is complete, active, and contains no extra spaces or quotation marks.

The model is not listed

The model ID must exactly match the name shown in the Cubicspaces console. Fully quit WorkBuddy, including its tray process, and reopen it.

Tool calling reports that reasoning_effort is unsupported

  1. Confirm that the endpoint is not configured as /v1/responses.
  2. Confirm that you are using a Cubicspaces environment where compatibility handling is deployed.
  3. Retain the request ID from the error and contact support.