- Demo is deployed and accessible at
/demos/chat-slotson the dashboard host - Agent backend is healthy (
/api/healthor/api/copilotkitGET);OPENAI_API_KEYis set on Railway;LANGGRAPH_DEPLOYMENT_URLpoints at a LangGraph deployment exposing the neutralsample_agentgraph (registered to thechat-slotsagent name) - Note: this demo DOES include
data-testidattributes on every custom slot. Use them as the primary selectors. The underlying agent is the neutral "helpful, concise assistant" (no frontend tools, no agent tools) — this demo exercises frontend slot customization only.
- Navigate to
/demos/chat-slots; verify the page renders a centered chat surface (max-width 5xl, full viewport height) within 3s - Verify the custom welcome screen is visible (
data-testid="custom-welcome-screen"), replacing the default welcome - Verify the nested welcomeMessage sub-slot renders inside the welcome screen (
data-testid="custom-welcome-message") with body text reading "Hover any region to see its slot path · click the badge to copy" - Verify the welcome card wraps the default chat
inputelement and asuggestionViewrow beneath it (both passed in as props by CopilotChatView)
- Confirm the welcome card displays a hoverable SlotMarker badge (the gradient indigo/violet ring) — visually distinct from the default CopilotChat welcome
- Confirm NO default CopilotChat welcome heading is rendered (the custom card fully replaces it)
- Verify two suggestion pills render in the
suggestionViewslot beneath the input with verbatim titles:- "Write a sonnet"
- "Tell me a joke"
- Click "Tell me a joke"; verify it sends the message "Tell me a short joke." and an assistant text response appears within 10s
- After sending the first message, verify the custom disclaimer renders below the chat input (
data-testid="custom-disclaimer") containing:- a small badge reading "slot" (indigo background, lowercase bold)
- body text "Custom disclaimer injected via
input.disclaimer." (the phraseinput.disclaimeris in monospace)
- Verify the default CopilotChat disclaimer text (if any) is NOT present — the custom disclaimer replaces it
- After the assistant response arrives, verify the assistant message is wrapped in the custom container (
data-testid="custom-assistant-message") with:- an indigo-tinted card background (
bg-indigo-50/60in light mode) - an indigo border (
border-indigo-200) - a small absolute-positioned "slot" badge at the top-left corner (indigo-600 background, white uppercase bold text)
- an indigo-tinted card background (
- Verify the user message bubble is NOT wrapped in the custom container (user messages use the default styling)
- Send a second prompt ("Write a one-line sonnet"); verify the second assistant response is also wrapped in the
custom-assistant-messagecontainer
- Attempt to send an empty message; verify it is a no-op (no user bubble, no network request)
- Send a ~500-character message; verify it wraps within the max-w-5xl container without horizontal scroll or layout break; the custom assistant-message card grows to fit the response
- Verify DevTools → Console shows no uncaught errors or missing-prop warnings during any flow above
- Chat surface renders within 3 seconds with the custom welcome card visible
- Assistant text response within 10 seconds; wrapped in the custom assistant-message slot on every turn
- All three custom slots (
welcomeScreen,input.disclaimer,messageView.assistantMessage) replace their defaults and are visually distinguishable via their "slot" badges / gradient styling - No UI layout breaks, no uncaught console errors