Attribution: who steered what
Every prompt and reaction in a MobSession is tagged with the sender's display name and a stable per-person color, so the team can see who is steering the agent.
MobSession tags every prompt and reaction with the name of the person who sent it. When a mob shares one agent, the team can always see who is steering, instead of staring at an anonymous wall of instructions.
How attribution works today
Every contribution carries the sender's name. Send a prompt and your display name shows up next to it. React to something, and that reaction gets tagged too. The orchestrator, the person coordinating the agent, has a name as well, so their turns are never anonymous.
Each name comes with a stable per-person color that holds for the whole session. After a few minutes you recognize a teammate by their color at a glance, which makes a busy transcript easy to scan: you can follow one person's thread without reading every line.
Display names today
You pick your display name when you join, and it sticks to everything you send for the rest of the session. No setup, so a mob can form in seconds.
Since you type your own name, treat attribution as a clarity and coordination feature, not an identity or security control. It tells you who's steering inside a trusted session. It does not prove a name belongs to a verified person.
The session as a record
The full transcript is captured while the session runs, and every contribution is attributed, so the session doubles as a record of who drove and what they asked for. Look back later and you'll see the sequence of prompts, who sent each one, and how the agent responded. That answers two questions at once: what was done, and who asked for it.
Why attribution matters for a mob
A mob moves fast, and steering changes hands often. Attribution gives the group:
- Shared awareness. Everyone sees who's driving and who just made a request, without anyone announcing it.
- Fewer collisions. When two people are about to push the agent in different directions, the colored names make the conflict obvious.
- Accountability without ceremony. Decisions trace back to the person who asked, so follow-up questions land in the right place.
- A readable history. Each line already says who said it, so the transcript stays legible after the fact.
What is coming in early access
Self-entered display names are the foundation. A few stronger capabilities are in early access and rolling out. Don't rely on them as shipped guarantees yet:
- Verified identity. SSO-backed identity that ties a session name to a real, authenticated person, so attribution becomes proof rather than a label.
- Persistent accounts. Profiles that carry your name and color across sessions.
- Saved and exportable history. Session transcripts and ROI reports you can save, revisit, and export.
- Audit logs, retention policies, and roles. Controls for teams that need governed access and a durable record.
Until verified identity ships for your team, keep treating display names as a coordination aid inside trusted sessions, not authentication.