@assistant-ui/mcp-docs-server 0.1.33 → 0.1.34

package/.docs/organized/code-examples/with-store.md

@@ -339,80 +339,80 @@ declare module "@assistant-ui/store" {
 
 import "./foo-scope";
 
-import { type ReactNode, useMemo } from "react";
-import { resource, tapMemo, tapState } from "@assistant-ui/tap";
+import { type ReactNode, useMemo, useState } from "react";
+import { resource } from "@assistant-ui/tap";
 import {
   useAui,
   useAuiState,
   AuiProvider,
-  tapClientList,
+  useClientList,
   Derived,
-  tapAssistantEmit,
+  useAssistantEmit,
   RenderChildrenWithAccessor,
   type ClientOutput,
 } from "@assistant-ui/store";
 
 type FooData = { id: string; bar: string };
 
-export const FooItemResource = resource(
-  ({
-    getInitialData,
-    remove,
-  }: tapClientList.ResourceProps<FooData>): ClientOutput<"foo"> => {
-    const emit = tapAssistantEmit();
+export const FooItemResource = resource(function FooItemResource({
+  getInitialData,
+  remove,
+}: useClientList.ResourceProps<FooData>): ClientOutput<"foo"> {
+  const emit = useAssistantEmit();
 
-    const [state, setState] = tapState<FooData>(getInitialData);
+  const [state, setState] = useState<FooData>(getInitialData);
 
-    const updateBar = (newBar: string) => {
-      setState({ ...state, bar: newBar });
-      emit("foo.updated", { id: state.id, newValue: newBar });
-    };
+  const updateBar = (newBar: string) => {
+    setState({ ...state, bar: newBar });
+    emit("foo.updated", { id: state.id, newValue: newBar });
+  };
 
-    const handleRemove = () => {
-      emit("foo.removed", { id: state.id });
-      remove();
-    };
+  const handleRemove = () => {
+    emit("foo.removed", { id: state.id });
+    remove();
+  };
 
-    return {
-      getState: () => state,
-      updateBar,
-      remove: handleRemove,
-    };
-  },
-);
+  return {
+    getState: () => state,
+    updateBar,
+    remove: handleRemove,
+  };
+});
 
 let counter = 3;
-export const FooListResource = resource(
-  ({ initialValues }: { initialValues: boolean }): ClientOutput<"fooList"> => {
-    const emit = tapAssistantEmit();
-
-    const foos = tapClientList({
-      initialValues: initialValues
-        ? [
-            { id: "foo-1", bar: "First Foo" },
-            { id: "foo-2", bar: "Second Foo" },
-            { id: "foo-3", bar: "Third Foo" },
-          ]
-        : [],
-      getKey: (foo) => foo.id,
-      resource: FooItemResource,
-    });
+export const FooListResource = resource(function FooListResource({
+  initialValues,
+}: {
+  initialValues: boolean;
+}): ClientOutput<"fooList"> {
+  const emit = useAssistantEmit();
+
+  const foos = useClientList({
+    initialValues: initialValues
+      ? [
+          { id: "foo-1", bar: "First Foo" },
+          { id: "foo-2", bar: "Second Foo" },
+          { id: "foo-3", bar: "Third Foo" },
+        ]
+      : [],
+    getKey: (foo) => foo.id,
+    resource: FooItemResource,
+  });
 
-    const addFoo = () => {
-      const id = `foo-${++counter}`;
-      foos.add({ id: id, bar: `New Foo` });
-      emit("fooList.added", { id: id });
-    };
+  const addFoo = () => {
+    const id = `foo-${++counter}`;
+    foos.add({ id: id, bar: `New Foo` });
+    emit("fooList.added", { id: id });
+  };
 
-    const state = tapMemo(() => ({ foos: foos.state }), [foos.state]);
+  const state = useMemo(() => ({ foos: foos.state }), [foos.state]);
 
-    return {
-      getState: () => state,
-      foo: foos.get,
-      addFoo,
-    };
-  },
-);
+  return {
+    getState: () => state,
+    foo: foos.get,
+    addFoo,
+  };
+});
 
 const FooProvider = ({
   index,
@@ -492,16 +492,16 @@ export default withAui(nextConfig);
   "dependencies": {
     "@assistant-ui/store": "workspace:*",
     "@assistant-ui/tap": "workspace:*",
-    "next": "^16.2.6",
-    "react": "^19.2.6",
-    "react-dom": "^19.2.6"
+    "next": "^16.2.7",
+    "react": "^19.2.7",
+    "react-dom": "^19.2.7"
   },
   "devDependencies": {
     "@assistant-ui/next": "workspace:*",
     "@assistant-ui/x-buildutils": "workspace:*",
     "@tailwindcss/postcss": "^4.3.0",
-    "@types/node": "^25.9.1",
-    "@types/react": "^19.2.15",
+    "@types/node": "^25.9.2",
+    "@types/react": "^19.2.17",
     "@types/react-dom": "^19.2.3",
     "postcss": "^8.5.15",
     "tailwindcss": "^4.3.0",
@@ -522,8 +522,8 @@ This is a Next.js application demonstrating the `@assistant-ui/store` package.
 ## Features Demonstrated
 
 - **Client Registry**: Module augmentation for type-safe client definitions
-- **tapClientList**: Managing lists with index and key lookup
-- **tapAssistantEmit**: Emitting and subscribing to scoped events
+- **useClientList**: Managing lists with index and key lookup
+- **useAssistantEmit**: Emitting and subscribing to scoped events
 - **Derived**: Creating derived client scopes from parent resources
 - **Provider Pattern**: Scoped access to list items via FooProvider
 - **Component Composition**: Render props pattern with components prop
@@ -587,10 +587,10 @@ declare module "@assistant-ui/store" {
 
 ```typescript
 const FooListResource = resource(
-  ({ initialValues }): ClientOutput<"fooList"> => {
-    const emit = tapAssistantEmit();
+  function FooListResource({ initialValues }): ClientOutput<"fooList"> {
+    const emit = useAssistantEmit();
 
-    const foos = tapClientList({
+    const foos = useClientList({
       initialValues: initialValues ? [/* ... */] : [],
       getKey: (foo) => foo.id,
       resource: FooItemResource,

package/.docs/organized/code-examples/with-tanstack.md

@@ -65,15 +65,15 @@
     "@assistant-ui/react": "workspace:*",
     "@assistant-ui/react-markdown": "workspace:*",
     "@tailwindcss/vite": "^4.3.0",
-    "@tanstack/react-router": "^1.170.10",
-    "@tanstack/react-start": "^1.168.18",
+    "@tanstack/react-router": "^1.170.15",
+    "@tanstack/react-start": "^1.168.25",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
     "lucide-react": "^1.17.0",
     "nitro": "^3.0.260311-beta",
-    "openai": "^6.39.1",
-    "react": "^19.2.6",
-    "react-dom": "^19.2.6",
+    "openai": "^6.42.0",
+    "react": "^19.2.7",
+    "react-dom": "^19.2.7",
     "remark-gfm": "^4.0.1",
     "tailwind-merge": "^3.6.0",
     "tailwindcss": "^4.3.0",
@@ -81,12 +81,12 @@
   },
   "devDependencies": {
     "@assistant-ui/x-buildutils": "workspace:*",
-    "@types/node": "^25.9.1",
-    "@types/react": "^19.2.15",
+    "@types/node": "^25.9.2",
+    "@types/react": "^19.2.17",
     "@types/react-dom": "^19.2.3",
     "@vitejs/plugin-react": "^6.0.2",
     "typescript": "^6.0.3",
-    "vite": "^8.0.14"
+    "vite": "^8.0.16"
   }
 }
 

package/.docs/organized/code-examples/with-tap-runtime.md

@@ -603,17 +603,17 @@ export default withAui(nextConfig);
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
     "lucide-react": "^1.17.0",
-    "next": "^16.2.6",
-    "react": "^19.2.6",
-    "react-dom": "^19.2.6",
+    "next": "^16.2.7",
+    "react": "^19.2.7",
+    "react-dom": "^19.2.7",
     "tailwind-merge": "^3.6.0"
   },
   "devDependencies": {
     "@assistant-ui/next": "workspace:*",
     "@assistant-ui/x-buildutils": "workspace:*",
     "@tailwindcss/postcss": "^4.3.0",
-    "@types/node": "^25.9.1",
-    "@types/react": "^19.2.15",
+    "@types/node": "^25.9.2",
+    "@types/react": "^19.2.17",
     "@types/react-dom": "^19.2.3",
     "postcss": "^8.5.15",
     "tailwindcss": "^4.3.0",

package/.docs/raw/docs/(docs)/architecture.mdx

@@ -56,60 +56,71 @@ Thread and message history can be stored by Assistant Cloud or by your own datab
 
 #### **1. Direct Integration with External Providers**
 
-```mermaid
-graph TD
+<Flow.Root
+  llm={`graph TD
     A[Frontend Components] --> B[Runtime]
-    B --> D[External Providers or LLM APIs]
-    
-    
-    classDef default color:#f8fafc,text-align:center
-    
-    style A fill:#e879f9,stroke:#2e1065,stroke-width:2px,color:#2e1065,font-weight:bold
-    style B fill:#93c5fd,stroke:#1e3a8a,stroke-width:2px,color:#1e3a8a,font-weight:bold
-    style D fill:#fca5a5,stroke:#7f1d1d,stroke-width:2px,color:#7f1d1d,font-weight:bold
-    
-    class A,B,C,D,E default
-```
+    B --> D[External Providers or LLM APIs]`}
+>
+  <Flow.Column>
+    <Flow.Node tone="pink">Frontend Components</Flow.Node>
+    <Flow.Arrow direction="down" length={36} />
+    <Flow.Node tone="blue">Runtime</Flow.Node>
+    <Flow.Arrow direction="down" length={36} />
+    <Flow.Node tone="red">External Providers or LLM APIs</Flow.Node>
+  </Flow.Column>
+</Flow.Root>
 
 #### **2. Using your own API endpoint**
 
-```mermaid
-graph TD
+<Flow.Root
+  llm={`graph TD
     A[Frontend Components] --> B[Runtime]
     B --> E[Your API Backend]
-    E --> D[External Providers or LLM APIs]
-    
-    
-    classDef default color:#f8fafc,text-align:center
-    
-    style A fill:#e879f9,stroke:#2e1065,stroke-width:2px,color:#2e1065,font-weight:bold
-    style B fill:#93c5fd,stroke:#1e3a8a,stroke-width:2px,color:#1e3a8a,font-weight:bold
-    style D fill:#fca5a5,stroke:#7f1d1d,stroke-width:2px,color:#7f1d1d,font-weight:bold
-    style E fill:#fca5a5,stroke:#7f1d1d,stroke-width:2px,color:#7f1d1d,font-weight:bold
-    
-    class A,B,C,D,E default
-```
+    E --> D[External Providers or LLM APIs]`}
+>
+  <Flow.Column>
+    <Flow.Node tone="pink">Frontend Components</Flow.Node>
+    <Flow.Arrow direction="down" length={36} />
+    <Flow.Node tone="blue">Runtime</Flow.Node>
+    <Flow.Arrow direction="down" length={36} />
+    <Flow.Node tone="red">Your API Backend</Flow.Node>
+    <Flow.Arrow direction="down" length={36} />
+    <Flow.Node tone="red">External Providers or LLM APIs</Flow.Node>
+  </Flow.Column>
+</Flow.Root>
 
 #### **3. With Assistant Cloud**
 
-```mermaid
-graph TD
+<Flow.Root
+  llm={`graph TD
     A[Frontend Components] --> B[Runtime]
     B --> C[Cloud]
     E --> C
     C --> D[External Providers or LLM APIs]
-    B --> E[Your API Backend]
-    
-    classDef default color:#f8fafc,text-align:center
-    
-    style A fill:#e879f9,stroke:#2e1065,stroke-width:2px,color:#2e1065,font-weight:bold
-    style B fill:#93c5fd,stroke:#1e3a8a,stroke-width:2px,color:#1e3a8a,font-weight:bold
-    style C fill:#86efac,stroke:#064e3b,stroke-width:2px,color:#064e3b,font-weight:bold
-    style D fill:#fca5a5,stroke:#7f1d1d,stroke-width:2px,color:#7f1d1d,font-weight:bold
-    style E fill:#fca5a5,stroke:#7f1d1d,stroke-width:2px,color:#7f1d1d,font-weight:bold
-    
-    class A,B,C,D,E default
-```
+    B --> E[Your API Backend]`}
+>
+  <Flow.Canvas
+    edges={[
+      { from: "runtime", to: "backend", route: "down", fromOffset: -20 },
+      { from: "runtime", to: "cloud", route: "down", fromOffset: 20 },
+      { from: "cloud", to: "providers", route: "down" },
+    ]}
+  >
+    <Flow.Column>
+      <Flow.Node tone="pink">Frontend Components</Flow.Node>
+      <Flow.Arrow direction="down" length={36} />
+      <Flow.Node flowId="runtime" tone="blue">Runtime</Flow.Node>
+      <div className="h-10" aria-hidden />
+      <Flow.Row>
+        <Flow.Node flowId="backend" tone="red">Your API Backend</Flow.Node>
+        <Flow.Arrow length={48} />
+        <Flow.Node flowId="cloud" tone="green">Cloud</Flow.Node>
+      </Flow.Row>
+      <div className="h-10" aria-hidden />
+      <Flow.Node flowId="providers" tone="red">External Providers or LLM APIs</Flow.Node>
+    </Flow.Column>
+  </Flow.Canvas>
+</Flow.Root>
 
 ## Going deeper
 

package/.docs/raw/docs/(reference)/api-reference/external-store/message-conversion.mdx

@@ -47,6 +47,6 @@ const unstable_convertExternalMessages: <T extends WeakKey>(messages: T[], callb
 ### unstable_createMessageConverter
 
 ```ts
-const unstable_createMessageConverter: <T extends object>(callback: useExternalMessageConverter.Callback<T>) => { useThreadMessages: ({ messages, isRunning, joinStrategy, metadata, }: { messages: T[]; isRunning: boolean; joinStrategy?: "concat-content" | "none" | undefined; metadata?: useExternalMessageConverter.Metadata; }) => ThreadMessage[]; toThreadMessages: (messages: T[], isRunning?: boolean, metadata?: useExternalMessageConverter.Metadata) => ThreadMessage[]; toOriginalMessages: (input: ThreadState | ThreadMessage | ThreadMessage["content"][number]) => unknown[]; toOriginalMessage: (input: ThreadState | ThreadMessage | ThreadMessage["content"][number]) => {}; useOriginalMessage: () => {}; useOriginalMessages: () => unknown[]; };
+const unstable_createMessageConverter: <T extends object>(callback: useExternalMessageConverter.Callback<T>) => { useThreadMessages: ({ messages, isRunning, joinStrategy, metadata, }: { messages: T[]; isRunning: boolean; joinStrategy?: JoinStrategy | undefined; metadata?: useExternalMessageConverter.Metadata; }) => ThreadMessage[]; toThreadMessages: (messages: T[], isRunning?: boolean, metadata?: useExternalMessageConverter.Metadata) => ThreadMessage[]; toOriginalMessages: (input: ThreadState | ThreadMessage | ThreadMessage["content"][number]) => unknown[]; toOriginalMessage: (input: ThreadState | ThreadMessage | ThreadMessage["content"][number]) => {}; useOriginalMessage: () => {}; useOriginalMessages: () => unknown[]; };
 ```
 {/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/external-store/runtime.mdx

@@ -28,6 +28,9 @@ import { ExternalStoreAdapter, ExternalThread, ExternalThreadProps, ExternalThre
 
 ### ExternalThreadQueueAdapter
 
+The queue surface a runtime exposes so the composer can stay usable during a
+run and render the pending messages.
+
 <ParametersTable {...ExternalThreadQueueAdapter} />
 
 ### pickExternalStoreSharedOptions

package/.docs/raw/docs/(reference)/api-reference/integrations/react-ai-sdk.mdx

@@ -36,6 +36,14 @@ const frontendTools: (tools: Record<string, ToolJSONSchema>) => ToolSet;
 
 ### generativeTools
 
+<Callout type="warn">
+<strong>Deprecated.</strong> Use [AISDKToolkit](/docs/api-reference/integrations/react-ai-sdk#aisdktoolkit) instead:
+`new AISDKToolkit({ toolkit }).tools({ frontend })`. It is a strict superset
+(it also opens MCP server connections), so it replaces `generativeTools`
+everywhere. The `frontendTools` option is named `frontend` on `.tools()`, and
+`.tools()` is async. `generativeTools` will be removed in a future version.
+</Callout>
+
 Builds an AI SDK `ToolSet` for server-side use with `streamText` /
 `generateText` from a generative `toolkit` and the frontend-uploaded tools.
 
@@ -44,15 +52,18 @@ Each toolkit tool's `execute` runs on the server. Pair this with the
 resolves to the server build — schema + `execute`, with `render` stripped) and
 pass it here. Tools without an `execute` are still exposed to the model but
 left for the client to fulfill. `frontendTools` lets the client contribute
-tools that aren't in the static toolkit. Use [AISDKToolkit](/docs/api-reference/integrations/react-ai-sdk#aisdktoolkit) when the
-toolkit contains MCP entries.
+tools that aren't in the static toolkit.
 
 ```ts
+// Define once at module scope so any MCP connections pool across requests.
+const aiToolkit = new AISDKToolkit({ toolkit: docsToolkit });
+
+// In your route handler:
 const { tools } = await req.json();
 streamText({
   model,
   messages,
-  tools: generativeTools({ toolkit: docsToolkit, frontendTools: tools }),
+  tools: await aiToolkit.tools({ frontend: tools }),
 });
 ```
 

package/.docs/raw/docs/(reference)/api-reference/tools/toolkits.mdx

@@ -3,7 +3,7 @@ title: Toolkits
 description: Define model-facing tools and compose them into named toolkits registered with an assistant-ui runtime scope.
 ---
 
-import { ToolDefinition, Tools, tool } from "@/generated/typeDocs";
+import { ToolDefinition, Tools, defineMcpToolkit, defineToolkit, providerTool, tool } from "@/generated/typeDocs";
 
 {/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
 {/* Do not edit manually. */}
@@ -63,7 +63,7 @@ Named collection of tools exposed to the assistant model.
 Keys are the tool names the model receives and uses in tool calls.
 
 ```tsx
-const toolkit = {
+const toolkit = defineToolkit({
   get_weather: {
     type: "frontend",
     description: "Get the weather for a city.",
@@ -71,7 +71,7 @@ const toolkit = {
     execute: async ({ city }: { city: string }) => fetchWeather(city),
     render: WeatherToolUI,
   },
-} satisfies Toolkit;
+});
 ```
 
 ```ts
@@ -88,4 +88,95 @@ context, while each tool renderer is registered with the tools scope for
 message rendering.
 
 <ParametersTable {...Tools} />
+
+### defineMcpToolkit
+
+Defines MCP server tools as a spreadable toolkit fragment.
+
+<ParametersTable {...defineMcpToolkit} />
+
+### defineToolkit
+
+Toolkit authoring helper. Accepts the permissive ToolkitDefinition
+(a generative `backend` tool may carry its server `execute`) and types the
+result as the canonical [Toolkit](/docs/api-reference/tools/toolkits#toolkit).
+
+In a `"use generative"` file, the compiler strips the wrapper per build so it
+can split schemas, renderers, and executors across the client/server boundary.
+Outside generative compilation, it returns the toolkit unchanged and can be
+used for plain frontend/backend/human toolkit objects.
+
+<ParametersTable {...defineToolkit} />
+
+### externalTool
+
+Marks a generative toolkit entry as an externally executed backend tool.
+
+Use this when another system (for example a backend route or LangGraph node)
+already defines and executes the tool, but assistant-ui should render its
+tool calls. The use-generative compiler omits `execute: externalTool()`
+entries from the server build and keeps a `type: "backend"` renderer on the
+client build.
+
+```ts
+function externalTool(): never;
+```
+
+### hitl
+
+<Callout type="warn">
+<strong>Deprecated.</strong> Use [humanTool](/docs/api-reference/tools/toolkits#humantool).
+</Callout>
+
+```ts
+const hitl: typeof humanTool;
+```
+
+### hitlTool
+
+<Callout type="warn">
+<strong>Deprecated.</strong> Use [humanTool](/docs/api-reference/tools/toolkits#humantool).
+</Callout>
+
+```ts
+const hitlTool: typeof humanTool;
+```
+
+### humanTool
+
+Marks a tool as **human-in-the-loop**: the agent pauses and the UI (`render`)
+supplies the result instead of code. Use it as the tool's `execute`:
+
+```tsx
+confirm: { execute: humanTool(), render: (props) => <Confirm {...props} /> }
+```
+
+Unlike [defineToolkit](/docs/api-reference/tools/toolkits#definetoolkit), it has **no runtime implementation**: a
+`"use generative"` compiler (e.g. `@assistant-ui/next` or `@assistant-ui/vite`)
+detects `execute: humanTool()`, drops it, and stamps the tool `type: "human"`.
+Reaching it at runtime means the module wasn't compiled (used outside a
+`"use generative"` file), so it throws.
+
+```ts
+function humanTool(): never;
+```
+
+### providerTool
+
+Marks a tool as provider-executed. The use-generative compiler converts
+`execute: providerTool(...)` into a `type: "provider"` tool entry.
+
+<ParametersTable {...providerTool} />
+
+### stubTool
+
+Marks a generative toolkit entry as a frontend tool whose executor will be
+supplied by `useAuiToolOverrides(...)`.
+
+`stubTool()` has no runtime implementation. It must be used inside a
+`"use generative"` toolkit file so the compiler can strip it.
+
+```ts
+function stubTool(): never;
+```
 {/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/utilities/miscellaneous.mdx

@@ -3,7 +3,7 @@ title: Utilities
 description: Miscellaneous @assistant-ui/react utilities for custom rendering, composition, and advanced assistant UI behavior.
 ---
 
-import { AssistantCloud, ChainOfThoughtClient, DevToolsHooks, InMemoryThreadList, SingleThreadList, defineMcpToolkit, defineToolkit, providerTool } from "@/generated/typeDocs";
+import { AssistantCloud, ChainOfThoughtClient, DevToolsHooks, InMemoryThreadList, SingleThreadList } from "@/generated/typeDocs";
 
 {/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
 {/* Do not edit manually. */}
@@ -22,60 +22,15 @@ import { AssistantCloud, ChainOfThoughtClient, DevToolsHooks, InMemoryThreadList
 
 <ParametersTable {...ChainOfThoughtClient} />
 
-### defineMcpToolkit
-
-Defines MCP server tools as a spreadable toolkit fragment.
-
-<ParametersTable {...defineMcpToolkit} />
-
-### defineToolkit
-
-Authoring helper for a `"use generative"` toolkit. Accepts the permissive
-ToolkitDefinition (a `backend` tool may carry its server `execute`)
-and types the result as the canonical [Toolkit](/docs/api-reference/tools/toolkits#toolkit).
-
-It has **no runtime implementation**. A `"use generative"` compiler (e.g.
-`@assistant-ui/next` or `@assistant-ui/vite`) strips the `defineToolkit(...)`
-wrapper (and its import) per build, so a correctly compiled
-`export default defineToolkit({...})` never calls this. If it *does* run, the
-module was not compiled by a use-generative loader — e.g. `defineToolkit` used
-outside a `"use generative"` file — which would ship a backend `execute` to the
-client. So it throws instead of silently leaking.
-
-<ParametersTable {...defineToolkit} />
-
-### DevToolsHooks
-
-<ParametersTable {...DevToolsHooks} />
-
-### hitl
-
-<Callout type="warn">
-<strong>Deprecated.</strong> Use [hitlTool](/docs/api-reference/utilities/miscellaneous#hitltool).
-</Callout>
+### createMessageQueue
 
 ```ts
-const hitl: typeof hitlTool;
+const createMessageQueue: (driver: MessageQueueDriver) => MessageQueueController;
 ```
 
-### hitlTool
-
-Marks a tool as **human-in-the-loop**: the agent pauses and the UI (`render`)
-supplies the result instead of code. Use it as the tool's `execute`:
-
-```tsx
-confirm: { execute: hitlTool(), render: (props) => <Confirm {...props} /> }
-```
-
-Like [defineToolkit](/docs/api-reference/utilities/miscellaneous#definetoolkit), it has **no runtime implementation**: a
-`"use generative"` compiler (e.g. `@assistant-ui/next` or `@assistant-ui/vite`)
-detects `execute: hitlTool()`, drops it, and stamps the tool `type: "human"`.
-Reaching it at runtime means the module wasn't compiled (used outside a
-`"use generative"` file), so it throws.
+### DevToolsHooks
 
-```ts
-function hitlTool(): never;
-```
+<ParametersTable {...DevToolsHooks} />
 
 ### InMemoryThreadList
 
@@ -87,13 +42,6 @@ function hitlTool(): never;
 const Interactables: () => ResourceElement<ClientOutput<"interactables">, undefined>;
 ```
 
-### providerTool
-
-Marks a tool as provider-executed. The use-generative compiler converts
-`execute: providerTool(...)` into a `type: "provider"` tool entry.
-
-<ParametersTable {...providerTool} />
-
 ### SingleThreadList
 
 A minimal threads scope that wraps a single thread.
@@ -102,18 +50,6 @@ Mounts the provided thread resource element.
 
 <ParametersTable {...SingleThreadList} />
 
-### stubTool
-
-Marks a generative toolkit entry as a frontend tool whose executor will be
-supplied by `useAuiToolOverrides(...)`.
-
-`stubTool()` has no runtime implementation. It must be used inside a
-`"use generative"` toolkit file so the compiler can strip it.
-
-```ts
-function stubTool(): never;
-```
-
 ### Suggestions
 
 ```ts