useFrontendTool
React hook for registering client-side tool handlers with optional UI rendering
Overview
useFrontendTool registers a client-side tool with CopilotKit at component scope. When the agent decides to call the tool, the provided handler function executes in the browser. Optionally, you can supply a render component to display custom UI in the chat showing the tool's execution progress and results.
The hook manages the full registration lifecycle: it warns if a tool with the same name already exists, registers the tool and its render component on mount, and cleans up both registrations on unmount. In v2, parameter schemas are defined using Zod instead of plain parameter arrays.
Signature
import { useFrontendTool } from "@copilotkit/react-core/v2";
function useFrontendTool<T extends Record<string, unknown>>(
tool: ReactFrontendTool<T>,
deps?: ReadonlyArray<unknown>,
): void;Parameters
Prop
Type
Prop
Type
Usage
Basic Tool with Zod Parameters
function TodoManager() {
const [todos, setTodos] = useState<string[]>([]);
useFrontendTool(
{
name: "addTodo",
description: "Add a new item to the user's todo list",
parameters: z.object({
text: z.string().describe("The todo item text"),
priority: z.enum(["low", "medium", "high"]).describe("Priority level"),
}),
handler: async ({ text, priority }) => {
setTodos((prev) => [...prev, text]);
return `Added "${text}" with ${priority} priority`;
},
},
[],
);
return (
<ul>
{todos.map((t, i) => (
<li key={i}>{t}</li>
))}
</ul>
);
}Tool with Custom Render Component
function WeatherWidget() {
useFrontendTool(
{
name: "getWeather",
description: "Fetch and display weather information for a city",
parameters: z.object({
city: z.string().describe("City name"),
units: z.enum(["celsius", "fahrenheit"]).default("celsius"),
}),
handler: async ({ city, units }, { signal }) => {
const response = await fetch(
`/api/weather?city=${city}&units=${units}`,
{ signal },
);
const data = await response.json();
return JSON.stringify(data);
},
render: ({ args, status, result }) => {
if (status === ToolCallStatus.InProgress) {
return (
<div className="animate-pulse">
Fetching weather for {args.city}...
</div>
);
}
if (status === ToolCallStatus.Complete && result) {
const data = JSON.parse(result);
return (
<div className="p-4 border rounded">
<h3>{data.city}</h3>
<p>
{data.temperature}° {data.units}
</p>
<p>{data.conditions}</p>
</div>
);
}
return null;
},
},
[],
);
return null;
}Conditionally Available Tool
function AdminPanel({ isAdmin }: { isAdmin: boolean }) {
useFrontendTool(
{
name: "deleteUser",
description: "Delete a user account by ID (admin only)",
parameters: z.object({
userId: z.string().describe("The ID of the user to delete"),
}),
handler: async ({ userId }) => {
await fetch(`/api/users/${userId}`, { method: "DELETE" });
return `User ${userId} deleted`;
},
available: isAdmin ? "enabled" : "disabled",
},
[isAdmin],
);
return <div>{/* admin UI */}</div>;
}Behavior
- Duplicate detection: If a tool with the same
nameis already registered, the hook logs a warning. Only one tool per name is active at a time. - Mount/Unmount lifecycle: The tool and its optional render component are registered on mount and removed on unmount.
- Dependency tracking: When
depsis provided, the tool registration is refreshed whenever any dependency value changes, similar touseEffect. - Render component lifecycle: If a
renderfunction is provided, it is added to the internal render tool calls registry. It receives streamingargs(partial duringInProgress, complete duringExecutingandComplete). - No return value: The hook returns
void.
Related
useHumanInTheLoop-- for tools that pause execution and wait for user inputuseRenderToolCall-- for rendering backend tool calls without a client-side handleruseComponent-- convenience wrapper for rendering React components from tool argsuseRenderTool-- register renderer-only tool call UI (named or wildcard)useCopilotAction-- v1 equivalent