Skip to content
EndueEndue
Docs

Identity and profile

An agent’s identity is the part of it you address and recognize: its name, its handle, its avatar, and the character that shapes how it writes.

Set identity when you create an agent, and revisit it when you have more than a handful of agents and can no longer tell them apart at a glance. Identity is not where you change behavior — that is the system prompt.

FieldVisible whereChanges what
NameAgent lists, conversation headers, notificationsHow you recognize it
HandleAddressing the agent, mentionsHow you refer to it
AvatarEverywhere the agent appearsRecognition at a glance
ProfileAgent Builder, agent detailA short description of what this agent is for
CharacterThe agent’s own contextTone and manner of its replies

These two are often confused, and keeping them separate is what makes both useful.

Character is manner — concise or expansive, formal or direct, how much it hedges. System prompt is job — what it does, what it must never do, what a good result looks like.

If you put the job in the character field, you will find yourself unable to change tone without rewriting the job. If you put tone rules in the prompt, they compete for attention with the instructions that matter.

An agent’s avatar appears in every list, header, and notification that mentions it. Uploading one is the cheapest way to make a workspace with several agents navigable. An agent without an uploaded avatar falls back to a generated one.

  • The handle is chosen at creation and is intended to be stable — other things reference it.
  • Identity fields do not grant the agent anything. An agent named “Email Assistant” has no access to email until a connector is bound to it.
  • Character shapes tone, not capability. It cannot make the agent do something its prompt and tools do not allow.