Model & Context
The Model & Context page contains settings that influence which AI model the agent uses for conversation and how much conversation history it "remembers."
Navigate to Conversation → Model & Context in the left sidebar.
Model Capability
Conversation AI Model
The primary AI model used for all user-facing conversation. This model handles every message the user sends and generates the visible response.
Choose based on the trade-off between response quality, speed, and cost:
| Consideration | Guidance |
|---|---|
| High accuracy required | Use the most capable model available |
| High volume / cost-sensitive | Use a smaller, faster model |
| Mixed needs | Enable User to Change AI Model below |
Enable User to Change AI Model
Allows end users to switch between different AI models during their conversation. When enabled, a model picker appears in the chat interface.
Allowed Conversation AI Models
Visible only when Enable User to Change AI Model is on. Select which models users are allowed to choose from. Users cannot pick a model outside this list.
The first model in the list becomes the default — it is the model the agent uses at the start of every conversation before the user makes a selection.
Enforce Thinking
When enabled, the AI is required to reason through its approach before generating the final response. This improves the quality of answers to complex or multi-step questions.
Use this for agents dealing with analysis, troubleshooting, or any task requiring careful reasoning.
Trade-off: Thinking adds latency. Responses take slightly longer to appear.
Context Window
These settings control how much of the conversation history the agent "remembers" when composing each response.
Summarize Previous Answer
When enabled, the agent summarizes its own previous responses before including them in the context window. This reduces the number of tokens used to represent prior turns, allowing longer conversations to fit within the model's context limit.
Use this for agents that handle extended multi-turn conversations.
Trade-off: Summaries may lose fine-grained detail from earlier answers. If precision in referencing past responses is important, keep this off.
Keep Function Tools Answer
When enabled, the output of any external tools or function calls (e.g., API responses, database query results) is retained in the conversation context for follow-up turns.
Use this when users are likely to ask follow-up questions about data retrieved by a tool (e.g., "Can you sort that by date?" after a database query).
User Messages to Carry Over
The number of recent user messages to include in the context window when starting a new conversation segment or after thread separation.
| Value | Behaviour |
|---|---|
0 | No history is carried into the new segment |
10 (default) | The last 10 user messages and their responses are included |
| Higher values | More continuity but higher token usage |
Set this based on how much conversational continuity matters for your agent and how long typical conversations are.
Saving Changes
Click Save after adjusting any setting. Publish your agent to propagate the changes to end users.