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

# Identity

> Agent persona, communication style, and responsibilities

`identity` adds human-facing context to an agent's system prompt. It influences how the model presents itself and approaches its stated responsibilities; it is not an automatic task router or scheduler configuration.

## Fields

| Field              | Type                   | Description                              |
| ------------------ | ---------------------- | ---------------------------------------- |
| `displayName`      | string                 | Human-readable name                      |
| `title`            | string                 | Job title or role label                  |
| `company`          | string                 | Organization name                        |
| `email`            | string                 | Identity metadata presented to the model |
| `bio`              | string                 | Short biography                          |
| `timezone`         | string                 | Timezone context presented to the model  |
| `avatar`           | string                 | Project-relative avatar path             |
| `responsibilities` | string\[] or object\[] | Areas the agent should focus on          |
| `tone`             | string                 | Communication style                      |
| `personality`      | string                 | Behavioral description                   |
| `socials`          | object                 | Named social profiles                    |

`email` does not configure SMTP and `timezone` does not alter mission schedules. Configure email credentials in the [Vault](/docs/agents/vault), and define schedule times explicitly.

Structured responsibilities use `area`, `description`, and `priority`:

```json theme={null}
{
  "identity": {
    "displayName": "Alex",
    "title": "Senior Backend Engineer",
    "company": "Acme Corp",
    "email": "alex@acme.dev",
    "timezone": "Europe/Rome",
    "tone": "Direct and concise",
    "personality": "Analytical and pragmatic",
    "responsibilities": [
      {
        "area": "API development",
        "description": "Design and maintain REST endpoints",
        "priority": "critical"
      },
      "Review server-side changes"
    ],
    "socials": {
      "github": "alex-eng"
    }
  }
}
```

Priority is prompt context and accepts `low`, `medium`, `high`, or `critical`. It does not implement deterministic assignment. Use `assignTo`, teams, or orchestration logic when routing must be explicit.

When `avatar` is set, Agent API responses enrich `identity` with a read-only `avatarUrl` for the Files API. `avatarUrl` is response metadata, not an `AgentIdentity` configuration field.

## Browser profiles

`browserProfile` belongs on the agent, outside `identity`:

```json theme={null}
{
  "name": "researcher",
  "browserProfile": "researcher-browser",
  "allowedTools": ["search_*", "browser_*"]
}
```

If omitted, the profile name defaults to the agent name. Cloud runs Chrome from sandbox-local storage and persists the profile archive under `.polpo/browser-profiles/{name}.tar.gz`. Browser profiles can contain authenticated session data and must be treated as credentials.