Overview
How might we design agent identity so people can trust and act on AI output?
When to use
- Essential for multi-agent platforms, enterprise AI deployments, and any ecosystem where users need to distinguish, version, and hold accountable specific agents across many interactions.
When to skip
- Single-assistant products where one global brand identity is enough.
- Background batch jobs that never surface in the user UI.
- Ephemeral one-off scripts with no reuse or marketplace presence.
Rules
Multiple agents that all look like the same generic bot avatar.
Renaming agents without version history, breaking audit references.
Capability claims in marketing copy that the runtime identity does not show.
Letting agents impersonate humans without an explicit agent label.
Evidence
| Product | Implementation |
|---|---|
| ChatGPT | Custom GPTs with names, icons, and instructions. |
| Claude | Projects and styled assistants with distinct context. |
| Microsoft Copilot Studio | Named copilots with published capability surfaces. |
| OpenAI Assistants API | Stable assistant IDs, names, and tool configurations. |