Model Switching

Summary

Choose a primary model from the models saved for the selected Bot. Other models may be fallbacks or saved without activation. Changing the model does not erase memory.

Before you start

Sign in, select the intended Bot and open Management → Model. The Bot must be ready. Web Chat does not require a messaging channel. Prepare a valid provider API key and available quota when using your own model.

Configure Models

Model Switching

Open Management → Model, expand the configured provider, and set the target model as primary. Wait for the primary marker, check model status and send a short test message in Web Chat. Selecting a dropdown value alone does not save the change.

If a scheduled-task update prompt appears, inspect the affected tasks and choose to update their model bindings, change only the chat model, or cancel. Tasks with unconfirmed bindings are not changed. Check the result after any synchronization.

Expand a configured provider to add another model and save it. Use the model-row actions to change the primary model, set or cancel fallback status, or delete a model. Deleting the last model under a provider also removes that provider configuration.

Troubleshooting

For 401 errors, verify the key, endpoint, protocol, region and plan type; Coding Plan and ordinary API credentials may differ. If saving is uncertain, refresh and inspect the saved configuration before retrying. Check quota and Diagnostics when chat still fails.