> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xpander.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Apps and Agents

> Manage the agent behind an Agentic Application: its identity, instructions, and runtime behavior.

This is where you manage the agent side of an Agentic Application: the backend that does the work. Omni agents are ready to use out of the box, but these controls let you shape a custom agent around your team’s exact workflow: its identity, instructions, runtime behavior, and output expectations, without rebuilding it from scratch.

<Frame caption="Agent settings bring a custom agent’s profile, model, skills, prompt, runtime, and controls into one place.">
  <img src="https://mintcdn.com/xpanderai-099931d1/ZExbmT2Yknjn6o_V/images/image-51.png?fit=max&auto=format&n=ZExbmT2Yknjn6o_V&q=85&s=a7dca34fa21b69680d6763a0a2aafd7c" alt="Agent settings panel showing a custom agent’s configuration" width="3024" height="1526" data-path="images/image-51.png" />
</Frame>

## Agent profile

The Agent Profile gives a custom agent its identity. It helps teammates understand what the agent does, who owns it, and whether it is the right agent for the work they want to delegate.

### Name

The name should describe the workflow the agent owns. Good names are specific and easy to recognize:

* `Stock & IPO Monitor`
* `RFP Response Agent`
* `Customer Escalation Agent`
* `Data Access Review Agent`

### Description

The description tells Omni and your teammates what the agent is designed to do. A strong description answers:

* What does the agent monitor or perform?
* What does it produce?
* Who is it useful for?

<Info>
  For a Stock & IPO Monitor, the description might explain that the agent tracks market news, top stock movers, IPO activity, and sends a daily digest.
</Info>

### Owner

The owner is responsible for the agent’s behavior and configuration. Ownership makes it clear who can review changes, answer questions, and improve the agent as the workflow evolves.

### Version

The version shows which revision of the agent you are viewing. Versions help teams understand when an agent changed, especially after updates to the prompt, model, skills, permissions, or publishing state.

<Frame caption="Track and switch between versions of an agent.">
  <img src="https://mintcdn.com/xpanderai-099931d1/ZExbmT2Yknjn6o_V/images/image-73.png?fit=max&auto=format&n=ZExbmT2Yknjn6o_V&q=85&s=8613b6c951bbce0eaf0dd5d599deff6b" alt="Agent version history" width="834" height="354" data-path="images/image-73.png" />
</Frame>

### Run mode

Run mode describes how the agent receives work. A custom agent may be used manually, discovered through Omni, triggered by developers, or connected to a scheduled or event-driven workflow.

## Prompt

The prompt is the agent’s operating instructions, applied every time it runs. Use it to define the agent’s role and the workflow it owns, the tools or data sources it needs, the structure its output should follow, and the quality rules, escalation behavior, and anything it should avoid.

<Frame caption="Use the prompt and runtime controls to refine how the agent behaves, reasons through long tasks, and returns results.">
  <img src="https://mintcdn.com/xpanderai-099931d1/ZExbmT2Yknjn6o_V/images/image-74.png?fit=max&auto=format&n=ZExbmT2Yknjn6o_V&q=85&s=e80e0614582e1502592b95e7fe7b0dc7" alt="Prompt and runtime controls for a custom agent" width="3022" height="1526" data-path="images/image-74.png" />
</Frame>

### Behavior rules

Behavior rules guide how the agent handles uncertainty, missing information, risk, and tool use. For example, the agent might ask for clarification when a request is ambiguous, avoid unsupported claims, prefer recent information for time-sensitive work, summarize sources when useful, and escalate when confidence is low.

### Output expectations

Output expectations make results consistent. For a Stock & IPO Monitor, the prompt might require a market summary, top gainers, an IPO watchlist, and major financial news, delivered as an email-ready digest with a clear subject line.

<Frame caption="Define what a good result should include.">
  <img src="https://mintcdn.com/xpanderai-099931d1/ZExbmT2Yknjn6o_V/images/image-75.png?fit=max&auto=format&n=ZExbmT2Yknjn6o_V&q=85&s=4f166a02250b8b9227b922a73803cf2c" alt="Output expectations for a custom agent" width="710" height="320" data-path="images/image-75.png" />
</Frame>

## Runtime

Runtime settings shape how an agent operates while a task is running. These controls are useful for agents that research, analyze, call tools, generate files, or work across multiple steps.

### Automatic context management

Automatic context management helps the agent stay focused during longer tasks. When enabled, Omni can compact older reasoning and tool output so the agent can continue working within the available context window.

<Frame caption="Automatic context management keeps the agent focused during longer tasks.">
  <img src="https://mintcdn.com/xpanderai-099931d1/ZExbmT2Yknjn6o_V/images/image-76.png?fit=max&auto=format&n=ZExbmT2Yknjn6o_V&q=85&s=5766592ab59856e139a4681ddee60978" alt="Automatic context management setting" width="702" height="122" data-path="images/image-76.png" />
</Frame>

### Advanced execution settings

Advanced execution settings provide deeper control over how the agent runs. Use them when a workflow needs more predictable behavior, specific execution constraints, or tighter control over tool-heavy tasks.