- Demo is deployed and accessible at
/demos/frontend-toolson the dashboard host - Agent backend is healthy (
/api/copilotkitGET returnslanggraph_status: "reachable");OPENAI_API_KEYis set;LANGGRAPH_DEPLOYMENT_URLpoints at a deployment exposing thefrontend_toolsgraph (registered under agent namefrontend_tools) - The backend
frontend_tools.pyregisters NO server-side tools — the agent forwards the frontend tool schema at runtime; the browser owns the handler - Frontend registers exactly ONE tool via
useFrontendTool:change_background(parameter:background: string— a CSS background value, colors or gradients). Handler sets local React state and returns{ status: "success", message: "Background changed to …" }
- Navigate to
/demos/frontend-tools; verify the page loads within 3s - Verify the background container (
data-testid="background-container") is visible, full-screen, flex-centered - Verify the initial background value is
var(--copilot-kit-background-color)(the theme default) — inspect the container's inlinestyle.background - Verify the
CopilotChatpanel renders centered (max width 4xl, rounded-2xl corners) inside the background container - Send "Hello"; verify the agent responds with plain text within 10s and does NOT call
change_background
- Verify the "Change background" suggestion pill is visible above the input
- Verify the "Sunset theme" suggestion pill is visible
- Click the "Change background" pill; verify it sends the verbatim prompt "Change the background to a blue-to-purple gradient."
- After clicking the "Change background" pill (or typing "Change the background to a linear gradient from indigo to pink"), verify within 15s that the agent invokes the
change_backgroundtool - Verify the
data-testid="background-container"element's inlinestyle.backgroundmutates fromvar(--copilot-kit-background-color)to a CSS gradient string containinglinear-gradient(orradial-gradient) - Verify the change is visually reflected (color/gradient swap is instant, no flash)
- Immediately after the background changes, verify the agent emits a follow-up assistant message that acknowledges the change
- Verify the follow-up message text references the new background value OR echoes the
"Background changed to <value>"success message (confirming the agent consumed the handler's return payload, not just triggered the tool blindly) - Ask "What color is the background right now?"; verify the agent replies with a description consistent with the last
change_backgroundcall's argument (demonstrates the agent received the handler's return string into context)
- Ask "Change it to a sunset gradient with orange and pink"; verify the background mutates again to a new gradient
- Verify the previous gradient is fully replaced (not layered)
- Ask "Now make it solid dark blue"; verify
style.backgroundbecomes a solid color value (e.g.#00008b,darkblue, orrgb(...)) — no gradient keyword
- Send "Change the background to banana"; verify the agent either (a) calls
change_backgroundwith a valid CSS fallback (e.g.yellow,#FFE135) and the container updates, or (b) declines politely without calling the tool — either is acceptable, but the UI must not crash - Send an empty message; verify it is a no-op
- Send a ~500-character prompt unrelated to backgrounds; verify the agent responds normally without invoking
change_background - Open DevTools → Console; verify no uncaught errors, no Zod parse failures, no
useFrontendToolwarnings
- Chat loads within 3 seconds; first
change_backgroundinvocation completes within 15 seconds of prompt - The
[data-testid="background-container"]inlinestyle.backgroundupdates in real time as the tool is invoked - Agent's follow-up reply demonstrably uses the handler's returned
messagefield (round-trip verified) - Multiple sequential invocations replace the background cleanly with no visual artifacts
- No uncaught console errors; no broken layouts