XDSChatSystemMessage@xds/core · Chat
Preview coming soon

Usage

XDSChatMessageList is the scrollable container for chat messages. It renders children in a flex column with role="log" for accessibility, provides density context to child messages, and supports infinite scroll for loading older messages. Use it inside XDSChatLayout for full-page chat with auto-scroll and composer docking, or standalone for embedded message panels.

Best practices

GuidancePractices
DoCompose messages using MessageList > Message > Bubble for consistent sender-aware styling and density.
DoSet the density prop to control spacing globally — compact for sidebars, balanced for most views, spacious for long-form reading. Individual messages can override.
DoUse the group prop on bubbles (first, middle, last) when a single sender sends multiple consecutive messages — it tightens corner radius to visually connect them.
DoUse XDSChatSystemMessage with variant="divider" for date separators and default for inline status notices like joins, leaves, or topic changes.
DoPut name on the first bubble and metadata on the last bubble in a message so they align with the bubble's inline padding.
DoProvide an emptyState prop so new users see a clear prompt to start a conversation instead of a blank screen.
DoUse the ghost bubble variant for AI-style responses that show rich content like code blocks or markdown without a visible boundary.
Don'tDon't use XDSChatSystemMessage for sender content — it has no avatar, alignment, or bubble. Use XDSChatMessage with a sender role instead.
Don'tDon't put long or multi-line content in a system message — keep it to a single short sentence. If you need more, use a bubble or a card.
Don'tDon't nest XDSChatMessage inside another XDSChatMessage — each message is a standalone article element with its own sender context.
Don'tDon't apply a fixed height directly on the message list — wrap it in a sized container and let the list fill with flex: 1.
Don'tDon't mix filled and ghost bubble variants within the same sender's messages — pick one style per side and use it consistently.
Don'tDon't place metadata or names on both the bubble and the message wrapper — pick one based on whether the content has a bubble boundary.

Anatomy

ElementDescription
Message arearequiredScrollable region for messages. Renders children (typically XDSChatMessageList) in a flex column that pushes content to the bottom when the list is short.
Frosted glass dockrequiredSticky or fixed container at the bottom with a backdrop-blur layer. Houses the scroll button and composer.
Scroll-to-bottom buttonAppears when the user scrolls up or new messages arrive. Defaults to XDSChatLayoutScrollButton; pass null to hide or a custom element to override.
ComposerrequiredThe input area for sending messages, typically XDSChatComposer. Docked at the bottom inside the frosted glass layer.
Empty stateCentered placeholder shown when no messages exist. Use XDSEmptyState for a consistent look.
AvatarA sender avatar rendered beside the message. Typically XDSAvatar with size="small". Hidden for system messages.
NameSender name above the message body. Place on the bubble when using bubbles, or on the message wrapper for raw content.
ContentrequiredThe message body — one or more XDSChatMessageBubble elements, or any free-form ReactNode like images or tool calls.
MetadataTimestamp, delivery status, and footer actions below the message. Place on the last bubble or on the message wrapper.

Import

ts
import {XDSChatSystemMessage} from '@xds/core/Chat'

Props

PropTypeDescription
childrenrequired
ReactNodeSystem message content — a short, factual string like a date, a join/leave notice, or a status change.
variant
'default' | 'divider' (default: 'default')Visual variant. 'default' renders centered text. 'divider' adds horizontal lines on each side via XDSDivider — use for date separators and section breaks.
icon
ReactNodeLeading icon that reinforces the message type. Wrap in XDSIcon for consistent sizing. Use for membership changes, encryption notices, or AI activity.

Examples

Common configurations, variations, and states.
ChatSystemMessage — IconSystem messages with a leading icon that reinforces the message type. Use icons to help users scan and identify message categories at a glance.
tsx
'use client';
import {XDSChatMessageList, XDSChatSystemMessage} from '@xds/core/Chat';
import {XDSIcon} from '@xds/core/Icon';
import {XDSStack} from '@xds/core/Layout';
import {XDSText} from '@xds/core/Text';
import {
LockClosedIcon,
ShieldCheckIcon,
SparklesIcon,
UserPlusIcon,
} from '@heroicons/react/24/outline';
export default function ChatSystemMessageWithIcon() {
return (
<XDSStack direction="vertical" gap={4}>
<XDSText type="supporting" color="secondary">
Icons reinforce the message type
</XDSText>
<XDSChatMessageList>
<XDSChatSystemMessage icon={<XDSIcon icon={UserPlusIcon} />}>
Jordan was added to the conversation
</XDSChatSystemMessage>
<XDSChatSystemMessage icon={<XDSIcon icon={LockClosedIcon} />}>
Messages are end-to-end encrypted
</XDSChatSystemMessage>
<XDSChatSystemMessage icon={<XDSIcon icon={SparklesIcon} />}>
Agent is generating a response…
</XDSChatSystemMessage>
<XDSChatSystemMessage icon={<XDSIcon icon={ShieldCheckIcon} />}>
Conversation verified by admin
</XDSChatSystemMessage>
</XDSChatMessageList>
</XDSStack>
);
}
ChatSystemMessage — Status UpdatesRealistic status messages in a conversation flow showing membership changes, timestamps, and resolution notices.
tsx
'use client';
import {XDSChatMessageList, XDSChatSystemMessage} from '@xds/core/Chat';
import {XDSIcon} from '@xds/core/Icon';
import {
CheckCircleIcon,
UserMinusIcon,
UserPlusIcon,
} from '@heroicons/react/24/outline';
export default function ChatSystemMessageStatusUpdates() {
return (
<XDSChatMessageList>
<XDSChatSystemMessage variant="divider">
March 14, 2026
</XDSChatSystemMessage>
<XDSChatSystemMessage icon={<XDSIcon icon={UserPlusIcon} />}>
Sarah Chen joined the conversation
</XDSChatSystemMessage>
<XDSChatSystemMessage>
Topic changed to "Q2 Launch Planning"
</XDSChatSystemMessage>
<XDSChatSystemMessage variant="divider">
March 15, 2026
</XDSChatSystemMessage>
<XDSChatSystemMessage icon={<XDSIcon icon={UserMinusIcon} />}>
Alex Rivera left the conversation
</XDSChatSystemMessage>
<XDSChatSystemMessage variant="divider">Today</XDSChatSystemMessage>
<XDSChatSystemMessage icon={<XDSIcon icon={CheckCircleIcon} />}>
Conversation marked as resolved
</XDSChatSystemMessage>
</XDSChatMessageList>
);
}
ChatSystemMessage — VariantsDefault and divider variants side by side. Use default for inline status updates and divider for date separators or section breaks.
tsx
'use client';
import {XDSChatMessageList, XDSChatSystemMessage} from '@xds/core/Chat';
import {XDSStack} from '@xds/core/Layout';
import {XDSText} from '@xds/core/Text';
export default function ChatSystemMessageVariants() {
return (
<XDSStack direction="vertical" gap={4}>
<XDSStack direction="vertical" gap={1}>
<XDSText type="supporting" color="secondary">
Default
</XDSText>
<XDSChatMessageList>
<XDSChatSystemMessage>
Alex joined the conversation
</XDSChatSystemMessage>
<XDSChatSystemMessage>
Conversation marked as resolved
</XDSChatSystemMessage>
</XDSChatMessageList>
</XDSStack>
<XDSStack direction="vertical" gap={1}>
<XDSText type="supporting" color="secondary">
Divider
</XDSText>
<XDSChatMessageList>
<XDSChatSystemMessage variant="divider">
March 15, 2026
</XDSChatSystemMessage>
<XDSChatSystemMessage variant="divider">Today</XDSChatSystemMessage>
</XDSChatMessageList>
</XDSStack>
</XDSStack>
);
}

Showcase source

tsx
'use client';
import {XDSChatMessageList, XDSChatSystemMessage} from '@xds/core/Chat';
export default function ChatSystemMessageShowcase() {
return (
<XDSChatMessageList>
<XDSChatSystemMessage variant="divider">
March 15, 2026
</XDSChatSystemMessage>
<XDSChatSystemMessage>Alex joined the conversation</XDSChatSystemMessage>
<XDSChatSystemMessage>Agent is thinking…</XDSChatSystemMessage>
<XDSChatSystemMessage variant="divider">Today</XDSChatSystemMessage>
<XDSChatSystemMessage>
Conversation marked as resolved
</XDSChatSystemMessage>
</XDSChatMessageList>
);
}