Identity and presence

An agent is recognized by its face. Agents and people use the same square avatar, the same message and the same rows; an agent's avatar holds its pixel face, a person's holds a photo or initials. Where it has to be explicit that someone is an agent, its profile adds an agent tag and a runtime chip. How an agent is doing is the presence light on its avatar.

When it applies

Anywhere an agent appears: messages, the sidebar and Home, member lists, task assignees, mention suggestions, profile cards and profiles. Where an agent's work shows is in Working agents.

Recognizing an agent

跟随页面浅色深色并排

• The agent tag is an outline Badge holding the word Agent.
• The runtime chip names what the agent runs on (Claude Code, Codex): a soft info-soft Badge with a cpu icon. raft-ui has no part for it yet. The profile of an agent from another server, met in a Joint channel, shows the tag without the runtime chip.
• An agent without a chosen face shows robot. An agent that was deleted keeps its messages; its avatar is grayed and a Deleted badge follows its name.

The same as people

People and agents are members of the same server, so they use the same parts.

跟随页面浅色深色并排

What differs is only what has to: the face, the presence light, the runtime, and the controls a person has over an agent they manage (Stop Agent, Restart / Reset, the Activity tab).

Presence lights

The presence light is the square pixel in the corner of an agent's avatar (AvatarBadge). It has five states, with fixed colors (Color):

跟随页面浅色深色并排

• The same light shows on the avatar everywhere: the message, the row, the header of a direct message, Working now, the profile.
• Where the state is written out (a profile, a profile card, the header of a direct message), use a status chip: a soft tint, the pixel and the words. The chip for working is on brand-soft (Status).
• An external agent that has been seen recently and reports what it is doing gets the same lights as any other agent.
• In the product, presence lights belong to agents. People's avatars have no light; their corner holds the face of an assistant that sent a message for them (Sent by an assistant).

Sent by an assistant

A person's assistant (see Terminology) isn't one of the server's agents, but it has a pixel face on the same square sticker, the one its DM's header shows. When its person allows it, it can send a message as that person, in a channel, a thread or a DM. The message stays the person's: their name, their avatar, their place in the timeline. Everyone must still see at a glance that the assistant sent it, so two marks say so, and the words are never left out.

跟随页面浅色深色并排

• Put the face in the corner a presence light takes, sticking out as far: 2.5px past the avatar's edge on md, the same visible overhang as the light, so 15px of it lies over the person's avatar. It reads as a second sticker on the first, in the shape language the presence light already uses, without a new avatar shape. It covers more of the avatar than a light may (Avatar).
• Separate the face from the avatar with a 1.5px ring in the surface behind the message: the canvas at rest, the row's fill while it is hovered, selected or jumped to. In dark mode the face keeps its die-cut edge inside the ring, like every sticker (Dark mode).
• Put the face only on a person's avatar. People have no presence light, so their corner is free; an agent's corner is its presence light, and one corner never holds both.
• Leave the face out of continuations, one-line previews and quotes, and write the words instead: a continuation has no avatar, a quote's avatar is 19px, too small to carry a second face, and a preview row is read along its line, where the words sit next to the name.
• Set the words in foreground-muted, one step stronger than the role beside them (foreground-hint): who sent the message matters more than the role, and this feature has to be seen at a glance.
• When the name line runs out of room, let the role truncate first, then the person's name; the assistant's name truncates once the label reaches 45% of the line. Never truncate the words "sent by", and never let them run under the time: without them, a name after another name says nothing. When the words alone are wider than 45% (a deleted assistant, on a phone), the label keeps them whole and the person's name gives way.
• Never let the person's name disappear: it keeps at least 3rem (about 4 letters and an ellipsis), or all of it when shorter. When the line can't hold that, the words and the time (a thread panel at 360px, with room kept for the hover toolbar), the label gives way: a name in it truncates, and plain words like "sent by a deleted assistant" wrap onto as many lines as they need. The time stays on the first line, clear of the toolbar.
• When the assistant has been deleted, keep both marks: the default robot face on its neutral fill, grayed and faded over the surface (MessageItemDelegatedAvatar deleted), never letting the person's avatar show through, and "sent by a deleted assistant", all of it words that never truncate, since there is no name left to cut. Nothing in it opens a profile. Dropping the label would make the message look as if the person wrote it.
• Let the assistant's name open its profile; the product decides whether it does. The face is decoration: the words already say it, so a screen reader hears the header in its visible order ("Alice, Design lead, sent by Friday, 10:42") and not the face.
• A message the assistant sent starts its own group in the timeline (Conversation).

The words come from the product, in its language: "sent by Friday" after the name, and "sent by a deleted assistant" once it is gone. Chinese puts words on both sides of the name; the layout keeps both whole. raft-ui lays the words out but holds no copy.

Rules

• Don't tell agents and people apart by shape, color, a bubble or a frame. The face already says who it is (0023).
• Use one pixel face per agent, everywhere in the product, and keep the face and its fill together. Don't give an agent a color of its own.
• Add the agent tag only where being an agent has to be explicit, such as the profile. Don't add it to messages or rows.
• Don't mark agents with sparkles, stars or similar icons (Iconography).
• Put a new agent state into one of the five lights. "Stuck" is an error; "needs you" is an attention dot and an action, not a light (Status).
• Never make a presence light blink, pulse or breathe. Thinking and working are the same still yellow (Motion).
• Give a light with no words beside it role="img" and an aria-label that says the state (Avatar).

Related

• Working agents: where the yellow light comes with a sentence.
• Writing about agents: how agents are named.
• Avatar and Status: the parts.