CopilotChat
Inline chat component you can place anywhere and size as needed.
"""PydanticAI agent with sales todos state, weather/query tools, and HITL scheduling.Upgraded from proverbs demo to full feature parity with shared tool implementations."""import jsonfrom textwrap import dedentfrom typing import Anyfrom pydantic import BaseModel, Fieldfrom pydantic_ai import Agent, RunContextfrom pydantic_ai.ag_ui import StateDepsfrom ag_ui.core import EventType, StateSnapshotEventfrom pydantic_ai.models.openai import OpenAIResponsesModelfrom dotenv import load_dotenvfrom tools import ( get_weather_impl, query_data_impl, manage_sales_todos_impl, get_sales_todos_impl, schedule_meeting_impl, search_flights_impl, build_a2ui_operations_from_tool_call,)from tools.types import Flightload_dotenv()# =====# State# =====class SalesTodosState(BaseModel): """Sales pipeline todos managed by the agent.""" todos: list[dict[str, Any]] = Field( default_factory=list, description="The list of sales pipeline todos", )# =====# Agent# =====agent = Agent( model=OpenAIResponsesModel("gpt-4.1-mini"), deps_type=StateDeps[SalesTodosState], system_prompt=dedent(""" You are a helpful sales assistant that helps manage a sales pipeline. The user has a list of sales todos that you can help them manage. You have tools available to add, update, or retrieve todos from the pipeline. You can also look up weather and query financial data. You can search flights and display rich A2UI cards (via search_flights tool). You can generate dynamic A2UI dashboards from conversation context (via generate_a2ui tool). When discussing sales todos, ALWAYS use the get_sales_todos tool to see the current list before mentioning, updating, or discussing todos with the user. """).strip(),)# =====# Tools# =====@agent.tooldef get_weather(ctx: RunContext[StateDeps[SalesTodosState]], location: str) -> str: """Get the weather for a given location. Ensure location is fully spelled out. Useful on its own for weather questions, and a great companion to `search_flights` — always consider checking the weather at a destination the user is flying to, and checking flights to any city whose weather the user has just asked about. """ return json.dumps(get_weather_impl(location))@agent.tooldef query_data(ctx: RunContext[StateDeps[SalesTodosState]], query: str) -> str: """Query financial database for chart data. Returns data suitable for pie or bar charts.""" return json.dumps(query_data_impl(query))@agent.toolasync def manage_sales_todos( ctx: RunContext[StateDeps[SalesTodosState]], todos: list[dict[str, Any]]) -> StateSnapshotEvent: """Manage the sales pipeline. Pass the complete list of sales todos.""" result = manage_sales_todos_impl(todos) ctx.deps.state.todos = result return StateSnapshotEvent( type=EventType.STATE_SNAPSHOT, snapshot=ctx.deps.state, )@agent.tooldef get_sales_todos(ctx: RunContext[StateDeps[SalesTodosState]]) -> str: """Get the current list of sales pipeline todos.""" return json.dumps(get_sales_todos_impl(ctx.deps.state.todos or None))@agent.tooldef schedule_meeting( ctx: RunContext[StateDeps[SalesTodosState]], reason: str, duration_minutes: int = 30) -> str: """Schedule a meeting. The user will be asked to pick a time via the UI.""" return json.dumps(schedule_meeting_impl(reason, duration_minutes))@agent.tooldef search_flights( ctx: RunContext[StateDeps[SalesTodosState]], flights: list[dict[str, Any]]) -> str: """Search for flights and display the results as rich cards. Return exactly 2 flights. Each flight must have: airline, airlineLogo, flightNumber, origin, destination, date (short readable format like "Tue, Mar 18" -- use near-future dates), departureTime, arrivalTime, duration (e.g. "4h 25m"), status (e.g. "On Time" or "Delayed"), statusColor (hex color for status dot), price (e.g. "$289"), and currency (e.g. "USD"). For airlineLogo use Google favicon API: https://www.google.com/s2/favicons?domain={airline_domain}&sz=128 """ result = search_flights_impl(flights) return json.dumps(result)@agent.tooldef generate_a2ui(ctx: RunContext[StateDeps[SalesTodosState]]) -> str: """Generate dynamic A2UI components based on the conversation. A secondary LLM designs the UI schema and data. The result is returned as an a2ui_operations container for the middleware to detect. """ from openai import OpenAI # Extract conversation messages from deps copilotkit_state = getattr(ctx.deps, "copilotkit", None) conversation_messages: list[dict] = [] context_entries: list[dict] = [] if copilotkit_state: if hasattr(copilotkit_state, "messages"): for msg in copilotkit_state.messages or []: role = msg.role.value if hasattr(msg.role, "value") else str(msg.role) if role in ("user", "assistant"): content = "" if hasattr(msg, "content"): if isinstance(msg.content, str): content = msg.content elif isinstance(msg.content, list): parts = [] for part in msg.content: if hasattr(part, "text"): parts.append(part.text) elif isinstance(part, dict) and "text" in part: parts.append(part["text"]) content = "".join(parts) if content: conversation_messages.append({"role": role, "content": content}) if hasattr(copilotkit_state, "context"): context_entries = copilotkit_state.context or [] context_text = "\n\n".join( entry.get("value", "") for entry in context_entries if isinstance(entry, dict) and entry.get("value") ) client = OpenAI() tool_schema = { "type": "function", "function": { "name": "render_a2ui", "description": "Render a dynamic A2UI v0.9 surface.", "parameters": { "type": "object", "properties": { "surfaceId": {"type": "string"}, "catalogId": {"type": "string"}, "components": {"type": "array", "items": {"type": "object"}}, "data": {"type": "object"}, }, "required": ["surfaceId", "catalogId", "components"], }, }, } llm_messages: list[dict] = [ { "role": "system", "content": context_text or "Generate a useful dashboard UI.", }, ] llm_messages.extend(conversation_messages) response = client.chat.completions.create( model="gpt-4.1", messages=llm_messages, tools=[tool_schema], tool_choice={"type": "function", "function": {"name": "render_a2ui"}}, ) if not response.choices[0].message.tool_calls: return json.dumps({"error": "LLM did not call render_a2ui"}) tool_call = response.choices[0].message.tool_calls[0] args = json.loads(tool_call.function.arguments) result = build_a2ui_operations_from_tool_call(args) return json.dumps(result)What is this?#
<CopilotChat> is the base prebuilt chat surface. Drop it in wherever you
want the chat to render and size it to fit your layout. <CopilotSidebar>
and <CopilotPopup> are both thin wrappers over the same primitives; if you
need a dedicated chat page or an inline pane alongside other content, this
is the component you want.
When should I use this?#
Use <CopilotChat> when you want:
- A full-bleed chat that fills its container
- An inline chat pane as part of a larger page
- A dedicated
/chatroute - Maximum layout freedom (no docked chrome or launcher)
For a collapsible docked chat, use CopilotSidebar. For a floating bubble that overlays content, use CopilotPopup.
Basic setup#
Wrap your app in <CopilotKit> once (the provider wires the runtime, session,
and agent registry) and render <CopilotChat> inside the layout of your
choosing:
<CopilotKit runtimeUrl="/api/copilotkit" agent="agentic_chat"> <div className="flex justify-center items-center h-screen w-full"> <div className="h-full w-full max-w-4xl"> <Chat /> </div> </div> </CopilotKit>Code example#
A self-contained component that renders the chat and wires in starter suggestions:
function Chat() { useConfigureSuggestions({ suggestions: [ { title: "Write a sonnet", message: "Write a short sonnet about AI." }, ], available: "always", }); return <CopilotChat agentId="agentic_chat" className="h-full rounded-2xl" />;}Common props#
<CopilotChat> is the root primitive. <CopilotSidebar> and <CopilotPopup>
accept the same slots and labels, plus a few wrapper-specific props.
| Prop | Description |
|---|---|
agentId | Agent slug the chat should talk to (must match an agent configured on the runtime). |
labels | User-facing copy — header title, placeholder, welcome, disclaimer. |
messageView | Slot for the message list — see slots. |
input | Slot for the composer area (text area, send button, disclaimer). |
scrollView | Slot for the scroll container (e.g. custom feather/gradient). |
suggestionView | Slot for the suggestion pills shown below messages. |
welcomeScreen | Slot for the empty-state. Pass false to disable. |
Styling#
<CopilotChat> is fully themable:
- CSS variables / class overrides — see CSS customization
- Slots (subcomponents) — see slots
- Fully headless — see headless UI
