Claude Desktop

Nội dung tài liệu kỹ thuật hiện được cung cấp bằng tiếng Anh.

Claude Desktop's third-party inference / Gateway mode has its own configuration panel. It does not read gateway routing from the Claude Code CLI's ANTHROPIC_BASE_URL or settings.json. Follow this guide for Desktop; use Claude Code for terminal commands.

Before you start

• Install or update Claude Desktop.
• Create a key in Workspace → API Keys.
• Copy the exact ID of a model with Messages from the Model Catalog.

The gateway route must support /v1/messages, streaming, and tool use. This configuration does not make every Uptech API model Desktop-compatible. Anthropic's third-party documentation describes Claude models; do not assume a non-Claude model will work merely because it appears in a list.

1. Open the Gateway configuration

On macOS, use the menu bar. On Windows, use the application menu at the top left of the sign-in screen:

1. Help → Troubleshooting → Enable Developer Mode.
2. After the app restarts, open Developer → Configure Third-Party Inference….
3. In Connection, select Gateway as the inference provider.

If organization policy makes the form read-only, ask the administrator to update that policy. Local configuration cannot override managed gateway settings. Official in-app configuration.

2. Enter the Uptech API connection

For this static-key setup, leave OIDC / interactive-sign-in fields unset. The base URL does not include /v1 or /v1/messages. Use the panel's connection test before applying. Gateway reference.

3. Configure the model list

Desktop discovery and the Uptech API catalog are different lists. Desktop can discover models through the gateway's /v1/models, but its automatic discovery filters for recognizable Claude IDs. A model missing from the picker does not, by itself, prove that the API key is invalid.

In the configuration panel's Mô hình section, use an explicit model list when you need to pin a gateway model ID. The corresponding inferenceModels value has this shape:

[
  {
    "name": "YOUR_MODEL_ID",
    "labelOverride": "My Uptech API model"
  }
]

Replace YOUR_MODEL_ID with the exact gateway ID. Enter the name and optional label in the panel's model-list editor; the JSON shows the field structure for exported configuration and is not a complete file to paste into claude_desktop_config.json. The first entry is the default. Apply and restart, then select the model in the app.

An explicit list controls selection; it does not convert protocols or provide missing model capabilities. For non-Claude models, confirm compatibility with Uptech API support first. Do not rename another model to a Claude ID to imply support. If your goal is to try a custom model through Messages, the Claude Code CLI guide provides a direct model-ID configuration.

Only enable extra context or tier capabilities after verifying the route supports them. Model-list configuration reference.

4. Apply and verify

Choose Apply locally to save the configuration on this device and relaunch into it. If the app does not relaunch, fully quit and reopen it. Use the configured Gateway startup option if prompted. You can export a managed configuration from the same panel for organization rollout.

Send a short request and check Nhật ký gọi API for the actual model, completed outcome, and usage. For Code or Cowork, also verify a tool action and a complete response. A successful connection test alone is not an end-to-end agent test.

CLI, Desktop, and MCP

Do not copy terminal exports into an MCP server definition. Being signed into ordinary Claude chat does not mean your requests are routed through Uptech API. Confirm the Gateway configuration and corresponding Uptech API logs. Desktop routing reference.

Troubleshooting

Related: Claude Code · Codex CLI · Usage and logs.