Slots (Subcomponents)

Customize Vue chat surfaces with named and scoped slots.

What is this?

Every CopilotKit Vue chat component is composed from named slots. Use them to replace one visible piece while retaining the runtime connection, reactive message state, streaming behavior, and the rest of the prebuilt surface.

Vue offers three practical levels of slot customization:

  1. Classes and attributes on the chat components: compose one of the chat components (CopilotChatMessageView, CopilotChatAssistantMessage, CopilotChatUserMessage, CopilotChatInput) and pass class or other attributes to it.
  2. Scoped-slot composition: consume the slot's data and actions while replacing only that part of the template.
  3. Custom components: render your own Vue component inside the slot.

Slots are recursive: a root message-view slot can render CopilotChatMessageView, whose assistant-message slot can render CopilotChatAssistantMessage, whose copy-button slot can replace one toolbar control.

What it looks like in code

The examples below replace the welcome screen, the assistant message card, and the input disclaimer.

Welcome screen slot

The welcome-screen slot replaces the empty state shown before the first message. Its scoped props include the input and suggestion actions, so a custom screen can still submit a message through the existing chat:

SupportChat.vue
<script setup lang="ts">
import { CopilotChat } from "@copilotkit/vue/v2";
</script>

<template>
  <CopilotChat>
    <template #welcome-screen="{ onSubmitMessage }">
      <section class="welcome-card">
        <h2>How can we help?</h2>
        <button type="button" @click="onSubmitMessage('Show my open tickets')">
          Show my open tickets
        </button>
      </section>
    </template>
  </CopilotChat>
</template>

Assistant message slot

Use the message-view slot to compose the chat components, then customize their own slots or events. This keeps the component hierarchy and provider ancestry intact:

SupportChat.vue
<script setup lang="ts">
import {
  CopilotChat,
  CopilotChatAssistantMessage,
  CopilotChatMessageView,
} from "@copilotkit/vue/v2";
</script>

<template>
  <CopilotChat>
    <template #message-view="{ messages, isRunning }">
      <CopilotChatMessageView :messages="messages" :is-running="isRunning">
        <template #assistant-message="{ message, messages: allMessages, isRunning: running }">
          <CopilotChatAssistantMessage
            :message="message"
            :messages="allMessages"
            :is-running="running"
          >
            <template #toolbar-items>
              <span class="reviewed-badge">Reviewed</span>
            </template>
          </CopilotChatAssistantMessage>
        </template>
      </CopilotChatMessageView>
    </template>
  </CopilotChat>
</template>

The message components expose further named slots for user messages, assistant toolbars and buttons, tool calls, reasoning messages, and activity messages. For activity rendering, CopilotChatMessageView first looks for activity-<activityType>, then activity-message.

Disclaimer slot

The input's disclaimer slot replaces the text below the composer while leaving the textarea, send button, attachments, and transcription controls alone:

<CopilotChat>
  <template #input="inputProps">
    <CopilotChatInput
      v-bind="inputProps"
      :mode="inputProps.inputMode"
      :tools-menu="inputProps.inputToolsMenu"
      :show-disclaimer="true"
    >
      <template #disclaimer>
        <p class="support-disclaimer">Responses may be inaccurate.</p>
      </template>
    </CopilotChatInput>
  </template>
</CopilotChat>

Tailwind Classes

Add class to the chat component you compose inside the scoped slot, or add classes to your own markup:

<CopilotChat>
  <template #message-view="{ messages, isRunning }">
    <CopilotChatMessageView
      class="rounded-xl bg-gray-50 p-4 dark:bg-gray-900"
      :messages="messages"
      :is-running="isRunning"
    />
  </template>
</CopilotChat>

Props Override

Bind props, listeners, and attributes to the chat component rendered inside the slot:

<CopilotChat>
  <template #message-view="slotProps">
    <CopilotChatMessageView
      v-bind="slotProps"
      class="my-custom-messages"
      data-testid="message-view"
    />
  </template>
</CopilotChat>

Custom Components

For full control, render your own component. It receives the scoped data you choose to pass through:

<CopilotChat>
  <template #message-view="{ messages, isRunning }">
    <CustomMessageView :messages="messages" :is-running="isRunning" />
  </template>
</CopilotChat>

Once you replace a complete slot, your component owns that part's rendering. Compose the chat components when you want to preserve CopilotKit's default behavior.

Nested Slots (Drill-Down)

Named slots nest through the chat components.

Two levels deep

Override the assistant toolbar while keeping the default message renderer:

<CopilotChat>
  <template #message-view="{ messages, isRunning }">
    <CopilotChatMessageView :messages="messages" :is-running="isRunning">
      <template #assistant-message="assistantProps">
        <CopilotChatAssistantMessage v-bind="assistantProps">
          <template #toolbar-items>
            <CustomToolbarAction />
          </template>
        </CopilotChatAssistantMessage>
      </template>
    </CopilotChatMessageView>
  </template>
</CopilotChat>

Three levels deep

Replace a specific toolbar button and keep its imperative action attached:

<CopilotChatAssistantMessage v-bind="assistantProps">
  <template #copy-button="{ onCopy }">
    <button type="button" @click="onCopy">Copy response</button>
  </template>
</CopilotChatAssistantMessage>

Labels

Use the labels prop on a prebuilt surface for text-only changes:

<CopilotChat
  :labels="{
    chatInputPlaceholder: 'Ask your agent anything…',
    welcomeMessageText: 'How can I help you today?',
    chatDisclaimerText: 'AI responses may be inaccurate.',
  }"
/>

Use slots for structure and behavior, and labels for the existing user-facing copy.

Available Slots

CopilotChat / CopilotSidebar / CopilotPopup

The chat surfaces expose these root slots. Most are scoped with the state and actions needed to preserve the default behavior:

SlotDescription
chat-viewComplete chat view, including message, input, suggestion, attachment, and transcription state.
message-viewMessage-list composition; receives messages and isRunning.
scroll-viewScroll container, scroll actions, suggestions, and bottom-button state.
inputComposer state plus submit, stop, attachment, and transcription actions.
suggestion-viewSuggestion collection, loading indexes, and selection action.
welcome-screenInitial empty state with input and suggestion data.
welcome-messageOnly the default welcome copy area.
interruptA pending interrupt and its resolver.

Every slot above works the same on CopilotChat, CopilotSidebar, and CopilotPopup.

CopilotSidebar and CopilotPopup additionally expose:

SlotDescription
headerModal header with open state and close actions.
toggle-buttonLauncher with isOpen, toggle, open, and close.

CopilotChatMessageView

SlotDescription
assistant-messageAssistant message plus the full message list and run state.
user-messageUser message.
reasoning-messageReasoning message plus message list and run state.
tool-call-<name>One named tool-call renderer.
tool-callFallback tool-call renderer.
activity-<type>One named activity-message renderer.
activity-messageFallback activity-message renderer.
message-before / message-afterMetadata-aware content around each message.
cursorStreaming cursor.

Message and input chat components

  • CopilotChatAssistantMessage exposes layout, message-renderer, tool-calls-view, toolbar, toolbar-items, and individual copy, feedback, read-aloud, and regenerate button slots.
  • CopilotChatUserMessage exposes layout, message-renderer, toolbar, toolbar-items, copy/edit buttons, and branch navigation.
  • CopilotChatInput exposes layout, text-area, disclaimer, add-menu-button, audio-recorder, and the send/transcription controls.

Use the narrowest slot that expresses the change. It preserves more built-in behavior and reduces the amount of state and accessibility wiring you own.

How is this guide?