Agent Identity
Distinct Faces for Distinct Agents
When supervisor-worker setups dispatch many specialist agents, every agent action, output, and reasoning step needs a distinct visual identity so the user can tell them apart at a glance. Avatar, color, and role label — used consistently across logs, dashboards, and outputs.
Framing
The problem
Multi-agent UIs collapse all agents into "the AI", making it impossible for the user to attribute actions, outputs, or reasoning to a specific agent.
The pattern
Give each agent a stable visual and named identity — avatar, color, role label — rendered consistently across every surface where its work appears.
Why chat breaks here
Chat shows one assistant voice; multi-agent reality has many — and the user needs to tell them apart at a glance, not by reading metadata.
Risks
Identity bloat (too many similar avatars) defeats the purpose; superficial naming can imply more specialization than actually exists.
Avoid when
The system runs a single agent and identity adds visual chrome without information.
Use when
Multiple agents act on the user behalf and the user needs to attribute actions and outputs to specific agents at a glance.
DOPE evaluation
- Directability
- Users can address, redirect, or pause individual agents by name
- Observability
- Every action and output carries a stable visual identifier of the agent that produced it
- Predictability
- The same agent always renders with the same identity across surfaces
- Explainability
- Each agent identity carries a role description and capability boundary
Closest neighbours
- CrewAI · Agent Cards (CrewAI) — Every agent gets a Name, Role, Goal, and Backstory rendered as a card in the playground. Outputs are tagged with the agent that produced them. The clearest production framing of distinct-agents-as-distinct-faces.
- Claude Code · subagents (Anthropic) — Specialist agents (code-reviewer, debugger, frontend-developer, etc.) defined by name + role + tool allowlist, plus a `color` frontmatter field that renders each subagent in its own display color in the task list and transcript. Every dispatched call surfaces the subagent name, so attribution survives across long sessions — the clearest shipping proof of color-coded agent identity.
- Manus AI · internal agent roles (Monica · Manus) — Internal Planner / Executor / Verifier architecture — distinct roles exist in the orchestration layer, but they are not consistently exposed as labelled agents in the user-facing live log. The gap between internal role separation and visible identity is exactly what this pattern names.
- AutoGen Studio · agent gallery (Microsoft Research) — Multi-agent orchestration with a gallery view: each agent rendered as a card with system prompt, tools, and history. Conversations between agents are visualised as labelled message flows.
FAQ
When should I use the Agent Identity pattern?
Multiple agents act on the user behalf and the user needs to attribute actions and outputs to specific agents at a glance.
When should I avoid the Agent Identity pattern?
The system runs a single agent and identity adds visual chrome without information.
What problem does Agent Identity solve?
Multi-agent UIs collapse all agents into "the AI", making it impossible for the user to attribute actions, outputs, or reasoning to a specific agent.
Why is chat the wrong fit for this?
Chat shows one assistant voice; multi-agent reality has many — and the user needs to tell them apart at a glance, not by reading metadata.
Related patterns
- Often paired with: Supervisor-Worker — When agents are decomposed, identity is what makes attribution legible — which agent did this, which agent decided that.
- Often paired with: Action Audit & Undo — Audit logs need actors. Agent Identity makes the actor visible per row, not just a generic AI label.
- Often paired with: Agentic Dashboard — The control room cannot supervise faces it cannot tell apart. Identity is the prerequisite for multi-agent oversight.