assistant-ui Tools

Always consult assistant-ui.com/llms.txt for the latest API.

A tool is a named capability the model can call. In assistant-ui you declare tools in a toolkit, a map whose keys are the tool names the model sees and whose values carry the schema, the executor, and the renderer. The supported authoring path is a "use generative" file compiled by a build plugin, which splits one file into a server build (schema plus backend executors) and a client build (schema plus renderers plus browser executors).

References

• ./references/toolkits.md -- authoring a toolkit end to end: kinds, renderers, toModelOutput, providerOptions, stubs, splitting and merging files, backendless
• ./references/tool-ui.md -- rendering states, useToolArgsStatus, deferred rendering, streaming args, ToolFallback and ToolGroup
• ./references/human-in-loop.md -- human tools, human() interrupts, and the full approval gate surface
• ./references/mcp-server.md -- server-side MCP servers and defineMcpToolkit
• ./references/mcp-apps.md -- rendering MCP App ui:// widgets with McpAppRenderer
• ./references/webmcp.md -- publishing frontend tools to the browser agent with unstable_useWebMcpProvider
• ./references/multi-agent.md -- sub-agent conversations inside a tool call
• ./references/legacy-component-apis.md -- the deprecated makeAssistantTool family and how to migrate off it

The authoring model