Identify where generation comes from
Our model access is managed through the CrushOn AI account and its applicable entitlements. Chub documents API connection choices, while SillyTavern documents connection types for hosted and locally served models.
With a connected client, the interface and the model provider can be separate. Opening a character card does not itself supply generation access. Check the selected endpoint, supported model and any provider account required by the configuration.
Review the definition after moving it
Fields, name markers, prompting formats and context construction can differ between tools. A card importing without an error does not guarantee that the greeting, examples and response boundaries will be interpreted in the same way.
Test the first exchange, the user's role and one piece of lore. Keep the intended model constant while reviewing compatibility. Otherwise, a change caused by a different model can be mistaken for a damaged definition.
Account for the connection's bill and secrets
Separate any client or service subscription from charges for model usage. A locally served model has different operational needs from a remote API. Do not assume that a free interface implies free generation.
Treat an API key as a credential. Keep it out of public cards, screenshots and shared conversations, and use the provider's own process if it needs replacement. That client configuration is not evidence that our project provides a public API or transferable membership.
Common questions
Does a chat client include the model automatically?
Not necessarily. A client can require a configured remote or local model connection. Identify the endpoint, provider conditions and cost separately from the interface.
More on this topicDoes a free client make model usage free?
No such general conclusion follows. The selected provider or locally served model has its own access, usage and operational conditions.
More on this topicWhy does a card change after I move it?
The destination's fields, prompt format, model and context handling can differ. Test the greeting and relevant instructions rather than assuming that a file alone preserves behaviour.
More on this topic