Choose an installed tool. Harness includes platform-tested screenshots; the other guides provide steps checked against official docs, field diagrams and verification tasks. CC Switch manages configuration; you still run an actual agent.
Choose an installed tool. Harness includes platform-tested screenshots; the other guides provide steps checked against official docs, field diagrams and verification tasks. CC Switch manages configuration; you still run an actual agent.
Connect your AI app, starting with the first reply.
Already have an app? Open its setup guide. To understand the basics first, start with APIs and models.
Already have DeepSeek Harness installed? Follow the screenshots to connect your API, choose a model and thinking level, receive a first reply, and try a tool.
Open the Harness walkthroughChoose an installed tool. Harness includes platform-tested screenshots; the other guides provide steps checked against official docs, field diagrams and verification tasks. CC Switch manages configuration; you still run an actual agent.
Suppose you ask: “Read this order, calculate the total, and save the result.” Several parts work together.
You enter requests, select a folder, and watch progress here. When the model asks to use a tool, Harness runs it with the required permission and returns the result to the model.
This guide uses DeepSeek. The model does the reasoning; Harness supplies tools such as reading and writing files.
Harness sends requests using the platform address and your key. You can check your balance and usage on the platform.
They are two ways to format communication, not two models. Think of describing the same task in chat messages or filling in a task form. Both sides must understand the format.
| API format | Plain-language explanation | Harness option |
|---|---|---|
| OpenAI Chat Completions | Organizes the conversation as messages: what you said, which tool the model requested, and what the tool returned. | openai-completions |
| OpenAI Responses | Uses separate types of records for text replies, tool calls, and tool results, so the app can handle each part of a task. | openai-responses |
OpenAI in the name refers to the interface format. If you select the DeepSeek model in this guide, DeepSeek still answers. Choosing an OpenAI format does not turn it into a GPT model.
Changing the format does not upgrade the model. Apps and models may support each format differently, so results depend on the combination. This test did not establish which gives better answers.
Yes. In Harness, we completed a file read, calculation, save, and read-back check. Harness tools perform the actions; the model uses the results to continue.
No. Both formats accepted effort requests for this model. You still need to enable the model’s effort levels in Harness, as shown in step 6. Changing formats does not enable the menu.
Follow the guide for that app and model. These results apply to the tested Harness and DeepSeek combination, not every tool or model.
Anthropic Messages is a third format commonly used by Claude Code. It is a message format, not a model. That client appends /v1/messages to the root, whereas the OpenAI-compatible examples include /v1 in their base URL. Our Codex guide uses Responses, the Harness example starts with Chat Completions, and Kimi Code follows its configured type. Follow the tool guide and confirm model support; changing format does not add tools or effort levels.
Already have DeepSeek Harness installed? Follow the screenshots to connect your API, choose a model and thinking level, receive a first reply, and try a tool.
The screenshots show the Chinese interface. Connection names and addresses are marked as teaching examples; keys are hidden. My API is a name you can choose yourself. API Base URL is a placeholder: replace it with the real address supplied by the platform.
You can use my-api for Provider ID and My API for the display name. They help you recognize this connection and do not have to match the platform brand.
Paste the complete, current API address from the platform. Do not substitute the homepage address or copy the placeholder in the screenshot.
Choose OpenAI Chat Completions, shown as openai-completions in this version.
Paste your complete platform key without extra spaces.
After filling in the four fields above, click 获取可用模型. Let the app fetch the list before choosing a model.
Our test returned deepseek-v4.1-flash-1017 and glm-5.2. Your available list may differ.
All models may be selected initially. Keep DeepSeek and deselect glm-5.2 for this walkthrough.
The chosen model returns to the connection form. This is the button label in the tested version.
This version has no graphical switch for effort levels. Click 打开配置文件 at the top right of settings and open settings.yaml in a text editor.
Under your My API provider, find deepseek-v4.1-flash-1017 and add reasoningEfforts as shown below. Do not edit a model with the same ID under another provider.
Save, then reopen the model menu. Restart Harness if it has not updated. If your version has Model options → Reasoning levels, you can configure the levels there.
Add reasoningEfforts only within the model entry you just created. Keep the existing address, credential reference, and other settings. This is a partial example: do not replace the whole file with it.
models:
- id: deepseek-v4.1-flash-1017
reasoningEfforts:
low: low
high: high
max: maxLeading spaces matter. Indent with spaces and keep low, high, and max spelled exactly as shown.
If the input asks you to choose a workspace (选择工作区), use Add workspace (添加工作区). Select a folder you allow the app to work in; an empty practice folder is a good start.
The screenshot uses harness-api-practice. You can choose another name. Continue when the folder name is visible.
With the My API model selected, click its name at the bottom right and open Reasoning levels (推理等级).
Start with High for everyday tasks; try Max for harder tasks and compare the results and usage on your own work.
After choosing High, High appears beside the model name. DeepSeek Flash in the image is a display name for the same model.
After you select High, the level appears beside the model name.
Displaying the menu and upstream handling of each level are separate checks. Tested Off, Low, High, and Max requests were accepted; the Off sample returned no reasoning usage. Higher levels may take longer and use more tokens, without guaranteeing a better answer.
Connect an installed local Codex client to your API. First distinguish a local client from a cloud task.
With your app already installed, open Self-service on this website and sign in. Create or view your own API key, copy the API address shown there, and copy an exact model ID from Models and pricing. A website homepage, account password or marketing name is not a substitute. Check both account balance and key allowance.
API_HOST, YOUR_API_KEY and YOUR_MODEL_ID below are placeholders: replace each before use. Follow this article on whether to keep /v1; do not append /chat/completions or /responses. Examples do not connect automatically or contain your key.
These file settings target Codex CLI and clients that read local configuration, not browser cloud tasks. For a mouse-driven setup, use the Codex branch of the CC Switch guide.
Open ~/.codex/config.toml on macOS/Linux, or %USERPROFILE%\.codex\config.toml on Windows. Start Codex once if the file is missing. Merge the example below. MY_API_KEY is a variable name, not the key itself.
https://API_HOST/v1responsesYOUR_MODEL_IDMY_API_KEYKeep a copy of your current file first. Update matching entries rather than adding duplicates, and preserve unrelated settings. Do not share a configuration or screenshot containing a real key.
model_provider = "my_api"
model = "YOUR_MODEL_ID"
[model_providers.my_api]
name = "My API"
base_url = "https://API_HOST/v1"
wire_api = "responses"
env_key = "MY_API_KEY"
requires_openai_auth = falseSet MY_API_KEY as shown below, enter the test folder in that same terminal, then run codex. You do not need to replace your existing auth.json. A desktop app launched from its icon may not inherit terminal variables; use CC Switch for that client instead.
When the configuration uses MY_API_KEY, set it in the same terminal from which you start the app. Enter your real key only on your computer. This example shows the syntax; the variable lasts for that terminal session.
export MY_API_KEY="YOUR_API_KEY"
codex$env:MY_API_KEY = "YOUR_API_KEY"
codexUse /model to confirm the model. Start with the default or Medium when available. Alternatively put model_reasoning_effort = "medium" at the top level of config.toml, before any [table]. Use only levels accepted by the chosen model.
Use OpenAI Responses with wire_api = "responses" and retain /v1 in Base URL. Do not copy the Harness Chat Completions choice here. The model also needs compatible streaming and tools; a successful chat alone is insufficient.
Create an empty test folder, choose it as the workspace and start a new chat. Confirm the new provider and model are selected, then send the prompt below. A normal reply without an error confirms basic connectivity, not every agent feature. Tests incur normal API usage.
Reply only: Connection successful.Expected: the app displays “Connection successful.” If you see a login page, an error or endless loading, use the checks below before sending again.
In that test folder, use a text editor to create hello.txt containing “API connection test 27”. Save it, then send the prompt below. If permission is requested, allow reading only this test folder.
Use the file-reading tool to open hello.txt in the current workspace and tell me its contents. Do not change any files.Expected: a visible tool execution reading hello.txt, followed by an answer containing API connection test 27. A text answer alone is not evidence of a tool call. You may remove the test folder afterwards.
Check that the address and complete key belong to the same service and that the key is active. Never send support a full key.
Check /v1, the exact model ID and the API format. A listed model is not a guarantee of support for every format.
Check balance, key allowance and request rate; follow the returned error. More thinking effort cannot fix a quota problem.
Check model tool support, workspace permissions and the tool execution error.
Check capability declarations, the model and client version. Thinking support does not necessarily include adjustable effort.
Configuration checked on 2026-11-08. Menus may change with updates; use these official references to verify details. Use the current connection information provided by this platform.
This is Claude Code, not the Claude chat website. Configure the local CLI with a Messages endpoint, or use CC Switch for a graphical setup.
With your app already installed, open Self-service on this website and sign in. Create or view your own API key, copy the API address shown there, and copy an exact model ID from Models and pricing. A website homepage, account password or marketing name is not a substitute. Check both account balance and key allowance.
API_HOST, YOUR_API_KEY and YOUR_MODEL_ID below are placeholders: replace each before use. Follow this article on whether to keep /v1; do not append /chat/completions or /responses. Examples do not connect automatically or contain your key.
Confirm that the platform currently offers Anthropic Messages for your chosen Claude model. A Chat Completions or Responses URL cannot be substituted directly.
Open ~/.claude/settings.json on macOS/Linux or %USERPROFILE%\.claude\settings.json on Windows. Merge the example env entries, retaining valid JSON and unrelated settings. Do not put a personal key in shared project settings.
ANTHROPIC_BASE_URL is the Messages root. For an address https://API_HOST/v1, this example uses https://API_HOST; preserve any additional platform-specific path as instructed. The client appends /v1/messages. Fill ANTHROPIC_AUTH_TOKEN with your platform key and ANTHROPIC_MODEL with a Messages-compatible model ID.
https://API_HOSTYOUR_API_KEYYOUR_MODEL_IDAnthropic MessagesKeep a copy of your current file first. Update matching entries rather than adding duplicates, and preserve unrelated settings. Do not share a configuration or screenshot containing a real key.
{
"env": {
"ANTHROPIC_BASE_URL": "https://API_HOST",
"ANTHROPIC_AUTH_TOKEN": "YOUR_API_KEY",
"ANTHROPIC_MODEL": "YOUR_MODEL_ID"
}
}Run claude in the test folder. Use /status to check the address and credential source, then /model to confirm the model. If the old subscription or service is active, check personal settings, environment variables and CC Switch before replacing anything.
For a supported Claude model, inspect effort options in /model, or use /effort in versions offering it. Missing controls call for checking the model, version and gateway support; Harness capability checkboxes do not apply here.
Create an empty test folder, choose it as the workspace and start a new chat. Confirm the new provider and model are selected, then send the prompt below. A normal reply without an error confirms basic connectivity, not every agent feature. Tests incur normal API usage.
Reply only: Connection successful.Expected: the app displays “Connection successful.” If you see a login page, an error or endless loading, use the checks below before sending again.
In that test folder, use a text editor to create hello.txt containing “API connection test 27”. Save it, then send the prompt below. If permission is requested, allow reading only this test folder.
Use the file-reading tool to open hello.txt in the current workspace and tell me its contents. Do not change any files.Expected: a visible tool execution reading hello.txt, followed by an answer containing API connection test 27. A text answer alone is not evidence of a tool call. You may remove the test folder afterwards.
Check that the address and complete key belong to the same service and that the key is active. Never send support a full key.
Check /v1, the exact model ID and the API format. A listed model is not a guarantee of support for every format.
Check balance, key allowance and request rate; follow the returned error. More thinking effort cannot fix a quota problem.
Check model tool support, workspace permissions and the tool execution error.
Check capability declarations, the model and client version. Thinking support does not necessarily include adjustable effort.
Configuration checked on 2026-11-08. Menus may change with updates; use these official references to verify details. Use the current connection information provided by this platform.
Kimi Code is the agent, not a restriction to Kimi models. With a third-party provider, your configuration chooses the model. This article covers the current CLI.
With your app already installed, open Self-service on this website and sign in. Create or view your own API key, copy the API address shown there, and copy an exact model ID from Models and pricing. A website homepage, account password or marketing name is not a substitute. Check both account balance and key allowance.
API_HOST, YOUR_API_KEY and YOUR_MODEL_ID below are placeholders: replace each before use. Follow this article on whether to keep /v1; do not append /chat/completions or /responses. Examples do not connect automatically or contain your key.
Run kimi --version. The current file is ~/.kimi-code/config.toml, or %USERPROFILE%\.kimi-code\config.toml on Windows. Older versions may use ~/.kimi; consult the docs for your installed version rather than editing both.
Merge the example below. provider = "my_api" must match [providers.my_api]. my-model is a local alias; model is the actual platform ID. The 32768 context value is an example, not a model specification: adjust it to confirmed limits.
openai / openai_responseshttps://API_HOST/v1YOUR_MODEL_IDMY_API_KEYKeep a copy of your current file first. Update matching entries rather than adding duplicates, and preserve unrelated settings. Do not share a configuration or screenshot containing a real key.
default_model = "my-model"
[providers.my_api]
type = "openai"
base_url = "https://API_HOST/v1"
api_key_env = "MY_API_KEY"
[models.my-model]
provider = "my_api"
model = "YOUR_MODEL_ID"
max_context_size = 32768api_key_env = "MY_API_KEY" explicitly reads that environment variable. Set it below, run kimi, then use /model to select my-model. /login signs into the official service and does not configure this platform.
When the configuration uses MY_API_KEY, set it in the same terminal from which you start the app. Enter your real key only on your computer. This example shows the syntax; the variable lasts for that terminal session.
export MY_API_KEY="YOUR_API_KEY"
kimi$env:MY_API_KEY = "YOUR_API_KEY"
kimitype = "openai" uses Chat Completions. Change to "openai_responses" only after confirming that route for your model. Both examples retain /v1 in the supplied platform address.
Recognized models usually get automatic capabilities. For an unrecognized alias, add capabilities = ["tool_use", "thinking"] under [models.my-model] only when supported. Declare support_efforts and default_effort from real capabilities; for a low/high model, use support_efforts = ["low", "high"] and default_effort = "low". A declaration cannot add a capability to a model.
Once low is confirmed for this model, add the separate [thinking] section below to select it. Change effort to another declared value when needed. A global effort overrides the model’s default_effort. Save, run /reload in an idle session, then send a test message.
[thinking]
enabled = true
effort = "low"Create an empty test folder, choose it as the workspace and start a new chat. Confirm the new provider and model are selected, then send the prompt below. A normal reply without an error confirms basic connectivity, not every agent feature. Tests incur normal API usage.
Reply only: Connection successful.Expected: the app displays “Connection successful.” If you see a login page, an error or endless loading, use the checks below before sending again.
In that test folder, use a text editor to create hello.txt containing “API connection test 27”. Save it, then send the prompt below. If permission is requested, allow reading only this test folder.
Use the file-reading tool to open hello.txt in the current workspace and tell me its contents. Do not change any files.Expected: a visible tool execution reading hello.txt, followed by an answer containing API connection test 27. A text answer alone is not evidence of a tool call. You may remove the test folder afterwards.
Check that the address and complete key belong to the same service and that the key is active. Never send support a full key.
Check /v1, the exact model ID and the API format. A listed model is not a guarantee of support for every format.
Check balance, key allowance and request rate; follow the returned error. More thinking effort cannot fix a quota problem.
Check model tool support, workspace permissions and the tool execution error.
Check capability declarations, the model and client version. Thinking support does not necessarily include adjustable effort.
Configuration checked on 2026-11-08. Menus may change with updates; use these official references to verify details. Use the current connection information provided by this platform.
Add your model service in WorkBuddy’s desktop settings without editing a configuration file.
With your app already installed, open Self-service on this website and sign in. Create or view your own API key, copy the API address shown there, and copy an exact model ID from Models and pricing. A website homepage, account password or marketing name is not a substitute. Check both account balance and key allowance.
API_HOST, YOUR_API_KEY and YOUR_MODEL_ID below are placeholders: replace each before use. Follow this article on whether to keep /v1; do not append /chat/completions or /responses. Examples do not connect automatically or contain your key.
Open Settings → Models, sometimes labelled Model management. In custom models, click Add model. Expand the account menu at the bottom left if the sidebar is collapsed.
Choose Custom API/provider. Enter the full OpenAI-compatible address supplied by the platform, normally including /v1, and your API Key. Do not retain another vendor’s preset URL or append /chat/completions.
Custom APIhttps://API_HOST/v1YOUR_API_KEYYOUR_MODEL_IDEnter the exact model ID, or fetch models first if that button is available. Enable tools, images and thinking only when supported. Use documented context/output limits. Leave Custom protocol off for this standard OpenAI-compatible setup.
If the form has Supported thinking effort, declare only supported levels and keep the default on Auto initially. Save, select this custom model in chat, then choose effort there. Quick/Balanced/Ultimate modes are not universal effort levels for custom models.
Click Save, start a new task, open the model picker near the input and choose the model under Custom models. Saving does not ensure the current chat switches. If greyed out, complete the address and API Key in settings.
Create an empty test folder, choose it as the workspace and start a new chat. Confirm the new provider and model are selected, then send the prompt below. A normal reply without an error confirms basic connectivity, not every agent feature. Tests incur normal API usage.
Reply only: Connection successful.Expected: the app displays “Connection successful.” If you see a login page, an error or endless loading, use the checks below before sending again.
In that test folder, use a text editor to create hello.txt containing “API connection test 27”. Save it, then send the prompt below. If permission is requested, allow reading only this test folder.
Use the file-reading tool to open hello.txt in the current workspace and tell me its contents. Do not change any files.Expected: a visible tool execution reading hello.txt, followed by an answer containing API connection test 27. A text answer alone is not evidence of a tool call. You may remove the test folder afterwards.
Check that the address and complete key belong to the same service and that the key is active. Never send support a full key.
Check /v1, the exact model ID and the API format. A listed model is not a guarantee of support for every format.
Check balance, key allowance and request rate; follow the returned error. More thinking effort cannot fix a quota problem.
Check model tool support, workspace permissions and the tool execution error.
Check capability declarations, the model and client version. Thinking support does not necessarily include adjustable effort.
Configuration checked on 2026-11-08. Menus may change with updates; use these official references to verify details. Use the current connection information provided by this platform.
CC Switch manages configurations. It does not answer prompts itself: after enabling a provider, run the agent it manages.
With your app already installed, open Self-service on this website and sign in. Create or view your own API key, copy the API address shown there, and copy an exact model ID from Models and pricing. A website homepage, account password or marketing name is not a substitute. Check both account balance and key allowance.
API_HOST, YOUR_API_KEY and YOUR_MODEL_ID below are placeholders: replace each before use. Follow this article on whether to keep /v1; do not append /chat/completions or /responses. Examples do not connect automatically or contain your key.
Select Codex or Claude Code in the sidebar, then + / Add provider. These tabs write different client configurations. Follow only the branch for your client below.
Choose custom configuration, name it My API and enter your own API Key. Do not retain a different API platform’s preset address. Check the target client before saving.
Choose Responses, use https://API_HOST/v1 and an available Responses model ID. Check wire_api = "responses" in the configuration preview. Select only effort levels supported by that model.
Responses · https://API_HOST/v1Messages · https://API_HOSTYOUR_API_KEYMy APIChoose Anthropic Messages, use the supplied Messages root (https://API_HOST here) and ANTHROPIC_AUTH_TOKEN. Sonnet/Opus/Haiku mappings are client slots: map them only to available, confirmed-compatible models.
Save, click Enable on the provider card and confirm it is active. Reopen the target client or terminal. Start with direct connection; local routing and aggregation are unnecessary for this setup. Perform the two checks below inside Codex or Claude Code. An enabled card alone does not prove connectivity.
Create an empty test folder, choose it as the workspace and start a new chat. Confirm the new provider and model are selected, then send the prompt below. A normal reply without an error confirms basic connectivity, not every agent feature. Tests incur normal API usage.
Reply only: Connection successful.Expected: the app displays “Connection successful.” If you see a login page, an error or endless loading, use the checks below before sending again.
In that test folder, use a text editor to create hello.txt containing “API connection test 27”. Save it, then send the prompt below. If permission is requested, allow reading only this test folder.
Use the file-reading tool to open hello.txt in the current workspace and tell me its contents. Do not change any files.Expected: a visible tool execution reading hello.txt, followed by an answer containing API connection test 27. A text answer alone is not evidence of a tool call. You may remove the test folder afterwards.
Check that the address and complete key belong to the same service and that the key is active. Never send support a full key.
Check /v1, the exact model ID and the API format. A listed model is not a guarantee of support for every format.
Check balance, key allowance and request rate; follow the returned error. More thinking effort cannot fix a quota problem.
Check model tool support, workspace permissions and the tool execution error.
Check capability declarations, the model and client version. Thinking support does not necessarily include adjustable effort.
Configuration checked on 2026-11-08. Menus may change with updates; use these official references to verify details. Use the current connection information provided by this platform.
First declare the model’s available thinking levels, then choose a level in chat. The two steps are shown below.
This version has no graphical switch for effort levels. Click 打开配置文件 at the top right of settings and open settings.yaml in a text editor.
Under your My API provider, find deepseek-v4.1-flash-1017 and add reasoningEfforts as shown below. Do not edit a model with the same ID under another provider.
Save, then reopen the model menu. Restart Harness if it has not updated. If your version has Model options → Reasoning levels, you can configure the levels there.
Add reasoningEfforts only within the model entry you just created. Keep the existing address, credential reference, and other settings. This is a partial example: do not replace the whole file with it.
models:
- id: deepseek-v4.1-flash-1017
reasoningEfforts:
low: low
high: high
max: maxLeading spaces matter. Indent with spaces and keep low, high, and max spelled exactly as shown.
With the My API model selected, click its name at the bottom right and open Reasoning levels (推理等级).
Start with High for everyday tasks; try Max for harder tasks and compare the results and usage on your own work.
After choosing High, High appears beside the model name. DeepSeek Flash in the image is a display name for the same model.
After you select High, the level appears beside the model name.
Displaying the menu and upstream handling of each level are separate checks. Tested Off, Low, High, and Max requests were accepted; the Off sample returned no reasoning usage. Higher levels may take longer and use more tokens, without guaranteeing a better answer.
Create hello.txt inside your practice folder and write a sentence you know. Then send Harness the request below.
If the activity log shows a file read and the answer matches the first line, you have completed a simple tool call. Receiving a normal chat reply alone does not verify tools.
If the input asks you to choose a workspace (选择工作区), use Add workspace (添加工作区). Select a folder you allow the app to work in; an empty practice folder is a good start.
The screenshot uses harness-api-practice. You can choose another name. Continue when the folder name is visible.
Check the complete API address, the validity of the key, and whether your network can reach the address.
Complete step 6 for the model you selected, then open the model menu again.
Check the selected workspace and whether the current mode allows file reads.
Check that the key was copied completely, then check both the account balance and the key’s own allowance.