Agent Settings

Configure retention, sharing, memory, and safety controls

Agent settings let you control how your agent stores data, who can access it, and what safety measures are in place. Because the platform is governed by design, these controls inherit from your organization’s central policies while letting you tune retention, access, and guardrails per agent.

Accessing Settings

1. Open any agent in Agent Creator
2. Go to the Settings section
3. Navigate between tabs for different configuration areas

General Settings

Basic agent configuration:

Setting	Description
Name	Display name for the agent
Description	What the agent does
Category	Organizational category
Tags	Keywords for discovery
Icon	Visual identifier

Sharing & Access

Control who can use your agent.

Visibility Levels

When you publish, choose visibility:

Level	Who Can Access
Private	Only you
Organization	Anyone in your organization
Public	All platform users
Restricted	Specific users or groups you choose

Managing Access

For restricted visibility:

1. Go to Settings > Sharing
2. Click Add Access
3. Search for users or groups
4. Select the access level
5. Save

Access Requests

When users request access to your agent:

1. You’ll receive a notification
2. Go to Settings > Sharing > Requests
3. Review the request and message
4. Approve or deny

Retention

Control how long data is kept.

Conversation Retention

How long to keep chat history:

• Inherit from organization - Use org-wide default
• Custom - Set specific retention period (7-365 days)
• No limit - Keep indefinitely

Document Retention

For uploaded files:

• Same options as conversation retention
• Applies to files attached in conversations

Artifact Retention

For generated content (code, documents):

• Controls how long canvas artifacts are stored

Retention settings affect only future data. Existing data follows the policy that was active when it was created.

Memory

Configure how your agent remembers information.

Session Memory

Remembers context within a conversation:

• Enabled by default for Light Agent and above
• Persists until conversation ends

Long-term Memory

Remembers information across conversations:

• Available for Full Agent and Orchestrator profiles
• Stores facts, preferences, and context
• Searchable by the agent for relevant memories

To configure:

1. Go to Settings > Memory
2. Enable long-term memory
3. Set the maximum memories to recall (default: 50)
4. Save

Long-term memory works best when you instruct the agent on what’s worth remembering. Add guidance in your Instructions.

Model Settings

Advanced model configuration:

Setting	Description
Model	Primary AI model to use
Fallback Models	Backup models if primary fails
Temperature	Randomness of the output (0 = deterministic, 1 = balanced, 2 = creative)
Max Response Tokens	Maximum length of a single reply (one LLM call). Different from Message Token Budget, which limits a whole message

Budget Limits

Control resource usage per message. Each of these budgets resets at the start of every new user message and is checked at the start of each internal turn, before the next LLM call — a turn already in flight is never killed mid-way. Leave a field empty to fall back to the profile default (see below); if no Max Turns is set at all, the platform’s built-in 50-turn hard cap still applies.

Limit	Unit	Default (global)	Description
Max Turns	LLM round-trips	10	Number of think→act→observe cycles the agent runs to answer one message before it stops and hands off to the fallback
Message Token Budget	Cumulative input + output tokens	20,000	Total tokens spent answering one message, summed across every internal turn and tool call. Cached input reads are weighted at 0.1×. Resets for each new message
Tool Call Budget	Tool invocations	15	Total tool calls the agent may make while answering one message

These budgets are per message, not per conversation — they bound the work an agent does to answer a single user turn (which may span many internal reasoning steps and tool calls), and start fresh on the next message. The conversation-wide ceiling is a separate mechanism, context_budget, below.

The “global” defaults above are the platform baseline. In practice each agent inherits the defaults of its profile (Simple, Workflow, Light, Full, Orchestrator), which the table below spells out. Values you set on the agent override both.

Defaults per profile

Higher profiles unlock more autonomy and therefore ship with larger budgets:

Profile	Max Turns	Message Token Budget	Tool Calls	Cost Budget
Simple	1	50,000	0	—
Workflow	10	100,000	10	—
Light Agent	10	100,000	15	—
Full Agent	30	300,000	50	$1
Orchestrator	50	300,000	100	$5

Orchestrators also cap delegation depth at 3 levels (Agent A → B → C) to prevent runaway sub-agent chains.

Conversation context ceiling

Separate from the per-message budgets above, context_budget (default 120,000 tokens) caps how large a single conversation’s live context can grow — the accumulated history + current request + tool schemas sent to the model on any one call. It is not exposed in the settings UI today; it comes from the profile / platform default.

• At 70% of the ceiling, the runtime compacts the oldest context proactively.
• At 100%, it attempts one emergency compaction; if the request still doesn’t fit, the turn fails with a “Request too large… start a new conversation” message instead of an opaque provider error.

Because context accumulates across turns, this is effectively the limit on how long one conversation can run before you need to start a fresh one — distinct from the per-message Message Token Budget, which caps the work done on a single message.

See Runtime Safeguards for what happens when a budget is reached and the other built-in protections that don’t require configuration.

Safety & Guardrails

Protect users and your organization.

Input Guardrails

Filter incoming messages:

• Profanity filter - Block offensive language
• PII detection - Warn about personal information
• Topic restrictions - Block certain subjects

Output Guardrails

Filter agent responses:

• Hallucination check - Flag uncertain claims
• Sensitive content - Block inappropriate responses
• Compliance check - Ensure regulatory adherence

Action Approval

Require confirmation for sensitive operations:

Policy	Behavior
Auto	Tools execute automatically
Always Ask	User confirms every tool call
Ask External	Confirm calls to external services
Ask First	Confirm first call, then auto

Configure per-tool or as a default for all tools.

Channels

Configure how your agent is accessed.

Web Chat

The default chat interface:

• Enabled by default
• Customizable welcome message
• Suggested prompts for users

API Access

Programmatic access:

1. Enable API access in Settings > Channels
2. Copy the endpoint URL
3. Use your API key to authenticate

Embeds

Embed the chat widget on websites:

1. Enable embedding
2. Configure allowed domains
3. Copy the embed code
4. Add to your website

Danger Zone

Irreversible actions:

Unpublish

Remove the agent from public access while keeping the draft:

1. Go to Settings > Danger Zone
2. Click Unpublish
3. Confirm

The agent becomes draft-only. Existing conversations are preserved.

Delete

Permanently remove the agent:

1. Go to Settings > Danger Zone
2. Click Delete Agent
3. Type the agent name to confirm
4. Click Delete

Deletion is permanent. All conversations, test cases, and analytics data will be lost.

Next Steps

Publish your agent

Make your agent available to others

View analytics

See how users interact with your agent