Models, devices, and run profiles

#Choose the model setup that fits your team

TK Copilot supports two model paths: subscribe to TK Copilot AI, or connect your own model service. Both paths work with Chat, AI Customer Service, and Affiliate, and you can switch later.

A Desktop must also remain online for ongoing business work. The model determines which AI handles the work, while the device determines which computer runs that Shop's tasks. Customer Service and Affiliate rules still belong in their respective business pages.

#1. Use a TK Copilot AI subscription

An account with an active TK Copilot AI subscription automatically sees TK Copilot AI under Connections → Model providers. The subscription credential and available model are configured automatically, so there is no separate API key to obtain or paste.

APP CAPTUREThe English light-theme Model providers page with the active provider, available models, and additional providers in one view.

Subscribers see one consistent model name: Flagship. It is the stable model entry point managed by TK Copilot. We maintain the underlying model selection, service routing, and future upgrades. You do not need to decide when a task requires a stronger model, when it should use a faster model, or reconfigure every Shop after an underlying model changes.

After activating TK Copilot AI, Chat and Shop workflows can use Flagship as their default. Override a specific Shop only when that workflow should deliberately use your own provider instead.

Review subscription status, renewal time, and remaining allowance under Account → Billing & subscriptions. If the allowance is exhausted or the subscription becomes inactive, Desktop will prompt you to renew. You may also switch to an already configured provider of your own.

#2. Connect your own model service

If your team already pays for another model subscription, has an API key, or wants to run models locally, open Connections → Model providers → Add key and choose the relevant option:

• Subscription: sign in to a currently supported model subscription, such as using a ChatGPT account for Codex;
• API key: connect a mainstream provider listed in the app, including OpenAI, Anthropic, Gemini, and DeepSeek;
• Local LLM: connect Ollama on this computer or your private network, then select an installed model;
• Custom: connect an OpenAI-compatible or Anthropic-compatible endpoint by entering its server address and model name.

The page shows the providers and sign-in methods supported by the current release. A provider may require an API key, OAuth sign-in, an active subscription plan, or a local server address. Follow the instructions shown in its setup form.

After adding a provider:

1. confirm that it appears as configured;
2. select the model you want to use;
3. activate it as the current default;
4. send a simple message in Chat to verify the connection and response.

#3. Your model credentials stay on the device

API keys, OAuth tokens, and proxy credentials that you add are saved in the current Desktop's operating-system keychain or encrypted local storage. They are not uploaded to TK Copilot as part of your account profile. When moving to another computer, reconnect these providers on the new device.

Local credential storage does not mean every model request stays on the computer:

• with TK Copilot AI, model requests are handled through the TK Copilot cloud model service;
• with your own cloud provider, Desktop uses the locally stored credential to send model requests to that provider;
• with local Ollama, inference requests go to the local or private-network address you configured.

A model usually needs the conversation or business context required to complete its task. Choose a provider that meets your organization's data policy. If inference must remain in an environment you control, use a local model or a compatible endpoint managed by your team.

#4. Choose a global default and optional Shop overrides

The global default is the right choice for most merchants. Start with one dependable default so Chat and any workflow without an explicit override can use it automatically.

Override the model in a Shop's AI Customer Service or Affiliate page only when:

• a Shop needs a different language;
• the team wants that workflow to use its own provider;
• a specific region, compliance policy, speed, or cost requirement applies.

A workflow set to Global default follows later changes to the default model. An explicit Shop-level selection remains unchanged. After switching, test with a representative Customer Service conversation or Affiliate task.

#5. Understand run profiles and capability boundaries

Open Account → Run profiles. System profiles already provide the capabilities required by common workflows, so the default is the best starting point. Create a custom profile only when the team needs stricter limits for a workflow or separate operating boundaries for different members.

APP CAPTUREThe English light-theme Run profiles section. System profiles are grouped by business surface and show the tools included in the selected profile.

A Run Profile and Business instructions solve different problems. The profile controls what the Agent can do; Business instructions explain how it should judge and act for this Shop. After changing a profile, run a real workflow again to confirm that the Agent can still complete the full process.

#6. Bind the business to a handling device

In the Shop's AI Customer Service or Affiliate page, bind that workflow to the current Desktop. Keep the device:

• signed in to the correct account;
• on a stable network;
• connected to an available model service;
• running TK Copilot instead of remaining signed out for long periods.

Customer Service and Affiliate are configured separately for the same Shop. Confirm each one instead of assuming that a device shown on one page also handles the other.

When moving to a new device, complete sign-in and model connection there before changing the business binding. Then verify the change with one test conversation or held task.

#7. Keep business rules in the right place

Models and devices are shared setup. Put specific operating rules in the corresponding business page:

• refund, reshipment, prohibited promises, and escalation conditions belong in AI Customer Service → Business instructions for the Shop;
• the Customer Service escalation account and recipient belong on the same page;
• Creator targeting, Samples, outreach, and approval boundaries belong in Affiliate settings and Campaigns;
• product facts and creative material belong in Product Knowledge.

Continue with Configure AI Customer Service or the Affiliate quick start.

#Troubleshooting

TK Copilot AI does not appear after subscribing

Confirm that Desktop is signed in to the same account that owns the TK Copilot AI subscription, then reopen Model providers. If it still does not appear, check the subscription status and network connection.

A model is configured, but the business does not run

A model is only one prerequisite. Check whether the Shop service is enabled, the workflow is bound to a device, and Desktop is online.

One Shop needs a different model

Override the model in that Shop's business settings instead of changing the global default. Validate the result with a representative task afterward.

A local model cannot connect

Confirm that Ollama is running, the server address is correct, and the selected model has been downloaded. Do not use a text-only model for a task that must read images.