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

# Create Agent

> Defining the identity, context, and execution mode of your AI Agent

The first step in building a Maitai Agent is defining its identity: what it does, how it executes, and where it lives in your hierarchy. Go to **Forge > Agents** and click **Create Agent**.

<img src="https://mintcdn.com/maitai-cbe2cd27/n3vZftkf-RZetjw5/images/forge/agents/Build_Agents_CreateAgent.png?fit=max&auto=format&n=n3vZftkf-RZetjw5&q=85&s=be1a8f0385125ec70585e6633630bc53" style={{width: '100%', height: 'auto'}} width="815" height="720" data-path="images/forge/agents/Build_Agents_CreateAgent.png" />

### Basic Setup

* **Name & Description**: Clearly identify the agent's purpose. The description does double duty, it helps you organize, and it's used as a routing signal whenever this agent is invoked as a [sub-agent](/build/agents/capabilities/subagent).
* **Execution Mode**: How the agent processes each request, **Reasoning** (full planning loop, the default) or **Route** (single-step capability selection). This is part of the agent's identity, set here at build time; you can change it later from the agent's **Configuration** tab, but not per-request. See [Execution Mode](/build/agents/execution_mode).
* **Application**: Associate the agent with an Application. This determines which context documents are available and where the agent's LLM traffic (including its [flow steps](/build/agents/agent_flow)) is monitored.
* **Base URL (Optional)**: A default host applied to all of this agent's [API Actions](/build/agents/capabilities/api_action), so individual actions only need relative paths. Actions can override it when needed.

### Drafts, versions, and releases

Agents are versioned. Edits in the Portal land on the agent's **draft**; when you're happy with it, **Publish** creates an immutable version (major / minor / patch, with release notes). You can label versions with named releases like `prod` and pin requests to a version or release from the SDK, unpinned requests run the current draft.

Manage versions from the agent's **Versions** tab; see [Agent Call](/sdk/agent_call) for pinning from code.

## Next

* Configure how it executes: [Execution Mode](/build/agents/execution_mode)
* Add tools/capabilities: [LLM Action](/build/agents/capabilities/llm_action) · [API Action](/build/agents/capabilities/api_action) · [Subagent](/build/agents/capabilities/subagent)
* Full walkthrough: [Build an Agent](/examples/build_agent)
* Call your agent from code: [Agent Call](/sdk/agent_call)
