Display components
Register React components that your agent can render in the chat.
What is this?
A display component is a React component that your agent can call as a tool. When the agent calls the tool, CopilotKit renders your component directly in the chat with the tool's arguments as props. You do not write a handler, and the user does not need to do anything.
import { useComponent } from "@copilotkit/react-core/v2";
import { Chart, ChartProps } from "./chart";
useComponent({
name: "showChart",
description: "Populate data and show the user a chart",
parameters: ChartProps,
render: Chart
});
When should I use this?
Use a display component when you want to:
- Display rich UI (cards, charts, tables) inline in the chat
- Show structured data from agent responses
- Render previews, status indicators, or visual feedback
- Let the agent present information beyond plain text
How it works in code
Forward browser tools to Claude
Frontend tools registered with useFrontendTool arrive in the AG-UI run
input. This demo's server calls the Anthropic Messages API directly for
runs that carry frontend tools, so it converts each AG-UI tool definition
into a Messages API tool schema first.
The published ClaudeAgentAdapter from @ag-ui/claude-agent-sdk needs
no such conversion. It registers each frontend tool on its own in-process
MCP tool server as mcp__ag_ui__<name>, allows it, and ends the run when
Claude calls it so the browser can execute the tool. Pass the run input to
the adapter and frontend tools work with no extra wiring.
function buildTools(tools: RunAgentInput["tools"]): Anthropic.Tool[] {
if (!tools || tools.length === 0) return [];
return tools.map((tool) => {
let inputSchema: Anthropic.Tool.InputSchema = {
type: "object",
properties: {},
};
if (tool.parameters) {
try {
const parsed =
typeof tool.parameters === "string"
? JSON.parse(tool.parameters)
: tool.parameters;
inputSchema = parsed as Anthropic.Tool.InputSchema;
} catch (parseErr) {
// Don't silently swap in an empty schema — Claude will then accept
// any input shape, which compounds whatever caller bug produced
// the malformed JSON. Warn loudly so the tool definition gets
// fixed instead of being papered over.
const message =
parseErr instanceof Error ? parseErr.message : String(parseErr);
console.warn(
`[agent_server] failed to parse tool.parameters for ${tool.name}; using empty schema. error=${message}`,
);
}
}
return {
name: tool.name,
description: tool.description ?? "",
input_schema: inputSchema,
};
});
}The display component receives the tool's arguments as typed props and mounts inline in the chat. Below is the bar chart from the demo. The agent sends the data, and the component draws it.
useComponent({
name: "render_bar_chart",
description: "Display a bar chart with labeled numeric values.",
parameters: barChartPropsSchema,
render: BarChart,
});Ask the agent for a chart, for example Show me a bar chart of quarterly sales for Q1, Q2, Q3, Q4. The chart renders in the chat with the data
that the agent filled in.
Without parameters
For simple components that don't need typed parameters, leave out
parameters. The component then accepts any props:
useComponent({
name: "showGreeting",
render: ({ message }: { message: string }) => (
<div className="rounded border p-3 bg-blue-50">
<p>{message}</p>
</div>
),
});Scoping to an agent
In multi-agent setups, pass agentId to scope a component to one agent:
useComponent({
name: "renderProfile",
parameters: z.object({ userId: z.string() }),
render: ProfileCard,
agentId: "support-agent",
});How is this guide?