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

# Agents

> Understand SuperEmber agent identities, configuration, scopes, tools, review, and runtime status.

Agents are persistent workers with an identity, purpose, instructions, model setting, capabilities, memory scope, workspace, and access boundary.

## Agent types

| Type                 | Purpose                                                                          |
| -------------------- | -------------------------------------------------------------------------------- |
| Personal Agent       | Private coworker for one user, with personal credentials, approvals, and memory. |
| Company AI           | Organization-wide general entry point and channel fallback.                      |
| Executive AI         | Protected coordination root across Team Agents.                                  |
| Team Agent           | Primary shared AI identity for one team.                                         |
| Workforce agent      | Persistent specialist beneath a Team Agent or eligible manager agent.            |
| Workflow-owned agent | Agent configuration controlled by a workflow step rather than Fleet.             |

## Status

| Status                     | Meaning                                                                |
| -------------------------- | ---------------------------------------------------------------------- |
| Active                     | Runtime is ready to receive work.                                      |
| Setting up or provisioning | SuperEmber is creating the runtime and credentials.                    |
| Pending link               | A channel-facing identity still needs its required channel connection. |
| Draft                      | The agent exists in Fleet but is not live.                             |
| Failed                     | Provisioning or runtime setup did not finish.                          |

## Identity and purpose

An agent's name and title help people recognize it. Its purpose tells both people and other agents when work should be handed to it.

Write purpose as a routing contract:

```text theme={null}
Investigates customer-support incidents, gathers evidence from approved systems, and drafts a customer-safe explanation with confidence notes.
```

## Configuration

The agent configuration panel covers:

* identity, title, purpose, and visual profile
* role and operating instructions
* model selection
* apps, skills, MCP servers, and other capabilities
* team and delegation relationships
* knowledge and memory behavior
* channels and advanced runtime settings

Changes to protected system identities are intentionally restricted.

## Delegation

Fleet reporting edges determine persistent delegation targets. A Team Agent can hand work to its direct workforce; a specialist can delegate further only when it has eligible direct reports and delegation is enabled.

Delegation does not grant unlimited authorization. The target agent's exact boundary-crossing tool calls still pass through automatic review and may pause for a human.

## Tools and review

Agents can use connected apps, skills, MCP servers, workspace files, schedules, knowledge tools, browser and sandbox capabilities, and workflow tools when enabled.

The capability existing on an agent does not mean every call executes automatically. SuperEmber reviews boundary actions against user intent and risk. See [Automatic review and escalations](/product/auto-review-and-escalations).

## Model selection

Each agent can follow the workspace default or use a supported override. Model availability, context, pricing, and defaults can change, so use the model picker as the current source of truth rather than relying on a fixed list in documentation.

## Related pages

* [Teams and Team Agents](/product/teams-and-team-agents)
* [Fleets](/product/fleets)
* [Customize an agent](/guides/customize-an-agent)
* [Memory](/product/memory)