LongCat's official documentation provides two ways to configure LongCat-2.5 in WorkBuddy through an OpenAI-compatible API: the UI and a configuration file.
Suitable tasks: Using LongCat-2.5 in WorkBuddy for conversation, coding, and other agent tasks.
Unsuitable tasks: Assessing model quality, speed, or cost; the source provides no evaluation data.
Applicable model version: LongCat-2.5.
Applicable client, agent, or API: WorkBuddy on Windows or macOS; OpenAI-compatible API.
Recommended reasoning tier and parameters: Not specified; the configuration example enables supportsReasoning and supportsToolCall.
When adding a custom model in WorkBuddy, enter:
| Field | Value |
|---|---|
| Provider | Custom or OpenAI-compatible |
| API URL | https://api.longcat.chat/openai/v1/chat/completions |
| API KEY | Your LongCat API Key |
| Model Name | LongCat-2.5 |
You can also use the following models.json, replacing the placeholder with your own key:
{
"models": [
{
"id": "LongCat-2.5",
"name": "LongCat-2.5",
"vendor": "LongCat",
"url": "https://api.longcat.chat/openai/v1/chat/completions",
"apiKey": "YOUR_LONGCAT_API_KEY",
"supportsToolCall": true,
"supportsReasoning": true
}
]
}Get an API Key from the LongCat platform, make sure the account has sufficient token quota, and install WorkBuddy.
In the model switcher for a new task, select Configure Custom Model. On the Add Model page, enter the fields above and save; or create or edit the user-level models.json, add the configuration above, and restart WorkBuddy.
Turn off Auto mode, select LongCat-2.5 from the model list, and start using it.
The documentation lists LongCat-2.5 as supporting OpenAI and Anthropic API formats, and uses an OpenAI-compatible API in its WorkBuddy example.
Configuration file locations: on macOS, ~/.workbuddy/models.json; on Windows, <User Home>\.workbuddy\models.json. The project-level file is <project root>/.workbuddy/models.json and takes precedence over the user-level configuration.
The source provides no quality, latency, or benchmark data.
This is official setup documentation, not a hands-on validation; no API call was made for this article.
The configuration file contains a key. Store it securely and do not commit a real key.
The documentation does not specify the WorkBuddy version or reasoning parameters; the UI and service configuration may change between versions.
If the model does not appear in the list, check the JSON syntax, UTF-8 encoding without a BOM, and file path, then fully restart WorkBuddy. For a 401 error, check that the LongCat API Key and URL are correct; for a 404 error, check the model ID and full API URL.
LongCat 2.5