@m6d/cortex-server 2.1.0 → 2.2.0

package/README.md

@@ -64,15 +64,29 @@ Only `database`, `model`, and `agents` are required for a minimal setup. `storag
 
 Each key in `agents` becomes a route prefix (e.g. `assistant` → `/agents/assistant/...`). Agents can define per-agent `systemPrompt`, `tools`, `backendFetch`, `loadSessionData`, `resolveRequestContext`, and lifecycle hooks (`onToolCall`, `onStreamFinish`).
 
-## Interactive tools
-
-Control-Center tools published with kind "interactive" are declared to the
-model as client-executed tools: the call streams to the widget, the run parks,
-and `POST /chat/:chatId/tools/:toolCallId/initiate` hands the widget its embed
-payload (never the model). When the widget answers, the server re-establishes
-the result through the tool's verify endpoint and applies the tool's result
-delivery masking before the model reads it. See
-`apps/cortex-cc/docs/interactive-tools.md` for authoring them.
+## Client tools
+
+A tool in an agent's `tools` with an `execute` function runs on the server. One
+without is a static client tool: it is declared to the model, the call streams
+to the widget, and the host app answers it via `hooks.onToolCall` (or a
+`toolComponents` entry calling `setOutput`).
+
+```ts
+const getBrowserTimezone = toolDefinition({
+    name: "getBrowserTimezone",
+    description: "Read the user's IANA time zone from their browser.",
+    inputSchema: z.object({}),
+}).client();
+// agents.sample.tools = [getBrowserTimezone]
+```
+
+Control-Center tools published with type "embedded" are the dynamic client
+tools: declared the same way, but the widget first calls
+`POST /chat/:chatId/tools/:toolCallId/initiate`, which runs the tool's endpoint
+server-to-server and hands the widget its embed payload (never the model).
+The result the embedded page reports back is relayed to the agent as-is —
+verifying it is the integrating backend's job. See
+`apps/cortex-cc/docs/client-tools.md` for authoring them.
 
 ## Requirements
 

package/contracts/README.md

@@ -4,18 +4,32 @@ The shapes both sides of a cortex boundary must agree on. Private on purpose —
 it never publishes; each publishable package carries its own copy:
 
 - `@m6d/cortex-server` and `@m6d/cortex-cli` publish raw source, so their
-  `prepack` vendors a copy of this directory into the tarball (`contracts/` and
+  `prepack` vendors a copy of `src/` into the tarball (`contracts/src/` and
   `src/contracts/` respectively), resolved there by their shipped tsconfig paths.
 - `@m6d/cortex-angular` and `@m6d/cortex-react` compile the parts they import
-  into their build artifacts.
+  into their build artifacts (angular's `vendor` copies the seam directories
+  into `src/internal/`).
 
-Three boundaries, one subpath each:
+## Layout
 
-| import                      | boundary                                                      |
-| --------------------------- | ------------------------------------------------------------- |
-| `@cortex/contracts/wire`    | chat client ↔ server (HTTP/WebSocket types)                   |
-| `@cortex/contracts/runtime` | cortex-cc console ↔ server runtime API (zod schemas)          |
-| `@cortex/contracts/graph`   | graph authoring (cli) ↔ server (vocabulary, helpers, clients) |
+Every seam is a directory: `src/<seam>/index.ts`, split into focused files
+under the directory where that helps (see `graph/`). The `exports` map is a
+single wildcard (`"./*": "./src/*/index.ts"`), so adding a seam is adding a
+directory — no manifest edit, no consumer tsconfig edit for wildcard-mapped
+consumers (server, cli, sample-server, cc).
+
+| import                           | boundary                                             | consumers                                               |
+| -------------------------------- | ---------------------------------------------------- | ------------------------------------------------------- |
+| `@cortex/contracts/wire`         | chat client ↔ server (HTTP/WebSocket types)          | server, client SDKs (`internal/client`, angular, react) |
+| `@cortex/contracts/client-tools` | embedded page ↔ chat widget handshake                | server, client SDKs                                     |
+| `@cortex/contracts/runtime`      | cortex-cc console ↔ server runtime API (zod schemas) | server, cortex-cc                                       |
+| `@cortex/contracts/rich-text`    | prompt/description grammar (mentions, variables)     | server, cortex-cc                                       |
+| `@cortex/contracts/graph`        | graph authoring (cli) ↔ server (vocabulary, helpers) | server, cortex-cli                                      |
+
+`src/graph/clients/` is the one deliberate exception to "contracts only":
+`neo4j.ts` and `embed.ts` are runtime I/O clients shared by the CLI and the
+server. They live here so there is exactly one copy, vendored the same way as
+everything else; they are re-exported through `@cortex/contracts/graph`.
 
 Everything is consumed as TypeScript source — no build, no dist. Nothing here
 has a runtime dependency beyond zod (for `/runtime`), and nothing here may grow

package/contracts/src/client-tools/index.ts

@@ -0,0 +1,56 @@
+/**
+ * The embed ↔ widget handshake for client tools.
+ *
+ * A page embedded by the chat widget (a hosted checkout, signing page, …)
+ * reports its outcome with:
+ *
+ *     window.parent.postMessage(
+ *         { type: "cortex:client-tool", status: "completed", reference: "session_123" },
+ *         "*",
+ *     );
+ *
+ * The widget accepts the message only when the event's origin matches the
+ * tool's configured `embedOrigin`. The payload is the page's claim, relayed to
+ * the agent as-is: cortex does not verify it, and anything that must actually
+ * be true lives in the integrating backend's own records.
+ *
+ * Like the wire seam, this file is compiled into the client SDKs and must stay
+ * free of runtime dependencies. It is also the spec any future SDK (Flutter)
+ * reimplements against.
+ */
+
+export const CLIENT_TOOL_MESSAGE_TYPE = "cortex:client-tool";
+
+export const CLIENT_TOOL_STATUSES = ["completed", "cancelled", "failed"] as const;
+
+export type ClientToolStatus = (typeof CLIENT_TOOL_STATUSES)[number];
+
+export type ClientToolHandshake = {
+    type: typeof CLIENT_TOOL_MESSAGE_TYPE;
+    status: ClientToolStatus;
+    /** Opaque id for the integrating backend's own bookkeeping (session id, envelope id, …). */
+    reference?: string;
+    /** Optional payload passed through to the agent as part of the tool result. */
+    result?: unknown;
+};
+
+/**
+ * Parse a `message` event into a handshake, or null when the origin doesn't
+ * match the tool's `embedOrigin` or the payload isn't a well-formed handshake.
+ * Call from the widget's `message` listener with `event.data` / `event.origin`.
+ */
+export function parseClientToolHandshake(data: unknown, origin: string, embedOrigin: string) {
+    if (origin !== embedOrigin) return null;
+    if (typeof data !== "object" || data === null) return null;
+    const message = data as Record<string, unknown>;
+    if (message["type"] !== CLIENT_TOOL_MESSAGE_TYPE) return null;
+    const status = CLIENT_TOOL_STATUSES.find((known) => known === message["status"]);
+    if (!status) return null;
+    const reference = message["reference"];
+    return {
+        type: CLIENT_TOOL_MESSAGE_TYPE,
+        status,
+        ...(typeof reference === "string" ? { reference } : {}),
+        ...(message["result"] !== undefined ? { result: message["result"] } : {}),
+    } satisfies ClientToolHandshake;
+}

package/contracts/src/graph/index.ts

@@ -0,0 +1,30 @@
+/**
+ * The graph contract — the knowledge-graph vocabulary, authoring types and
+ * clients that `@m6d/cortex-cli` writes with and `@m6d/cortex-server` reads
+ * with. `@m6d/cortex-server` re-exports all of it, so a project authoring
+ * domains still has exactly one import path.
+ */
+
+export type { GraphSchema } from "./schema";
+export { GRAPH_SCHEMA, GRAPH_SCHEMA_VERSION } from "./schema";
+
+export type {
+    EndpointScalarType,
+    EndpointProperty,
+    ResponseKind,
+    AutoGenerated,
+    ConceptDef,
+    EndpointDef,
+    EndpointInput,
+    ServiceDef,
+    RuleDef,
+    DomainDef,
+} from "./types";
+
+export { defineConcept, defineRule, defineService, defineDomain, defineEndpoint } from "./helpers";
+
+export type { Neo4jConfig, Neo4jClient } from "./clients/neo4j";
+export { createNeo4jClient } from "./clients/neo4j";
+
+export type { EmbedFn, EmbeddingProviderConfig } from "./clients/embed";
+export { createEmbedder } from "./clients/embed";

package/contracts/{runtime.ts → src/runtime/index.ts}

@@ -90,16 +90,15 @@ export const knowledgeChunkSchema = z.object({
 });
 
 /**
- * Runtime contract §5.4: present on signatures of `interactive` tools — flows
+ * Runtime contract §5.4: present on signatures of `embedded` tools — flows
  * the end user completes in an embedded surface inside the chat widget. The
  * tool's endpoint fields act as the *initiate* call (returns the embed URL);
- * `hasVerify` marks a second, server-trusted call that settles the result.
+ * the result the page reports back is relayed as-is — verifying it is the
+ * integrating backend's job.
  */
-export const toolInteractionSchema = z.object({
+export const toolEmbedSchema = z.object({
     surface: z.enum(["inline", "modal"]),
     embedOrigin: z.url(),
-    hasVerify: z.boolean(),
-    resultDelivery: z.enum(["agent", "endpoint", "both"]),
 });
 
 export const toolSignatureSchema = z.object({
@@ -111,8 +110,8 @@ export const toolSignatureSchema = z.object({
     signature: z.string(),
     score: z.number().nullable(),
     pinned: z.boolean(),
-    interaction: toolInteractionSchema.optional(),
-    /** Interactive tools only: the published input JSON Schema, verbatim.
+    embed: toolEmbedSchema.optional(),
+    /** Client tools only: the published input JSON Schema, verbatim.
      * Client-executed declarations need a real schema — the rendered
      * `signature` text alone is not enough for function calling. */
     inputSchema: z.record(z.string(), z.unknown()).optional(),
@@ -212,9 +211,6 @@ export const searchKnowledgeResponseSchema = z.object({
 
 export const executeRequestSchema = z.object({
     input: z.record(z.string(), z.unknown()).default({}),
-    // Interactive tools only: absent | "initiate" targets the tool's endpoint
-    // fields, "verify" targets its verify endpoint config.
-    phase: z.enum(["initiate", "verify"]).optional(),
     context: z
         .object({
             threadId: z.string().max(128).optional(),
@@ -257,7 +253,7 @@ export const runtimeErrorSchema = z.object({
     }),
 });
 
-export type ToolInteraction = z.infer<typeof toolInteractionSchema>;
+export type ToolEmbed = z.infer<typeof toolEmbedSchema>;
 export type RuntimeAgentConfig = z.infer<typeof runtimeAgentConfigSchema>;
 export type ResolveRequest = z.input<typeof resolveRequestSchema>;
 export type ResolveResponse = z.infer<typeof resolveResponseSchema>;

package/contracts/{wire.ts → src/wire/index.ts}

@@ -71,16 +71,14 @@ export type TokenUsage = {
 };
 
 /**
- * How to launch one interactive tool: stamped by the server, per tool name, on
+ * How to launch one client tool: stamped by the server, per tool name, on
  * the metadata of an assistant message that may carry its pending call. Kept in
  * the message so the binding survives server restarts while a run is parked.
  */
-export type InteractiveToolBinding = {
+export type ClientToolBinding = {
     toolId: string;
     surface: "inline" | "modal";
     embedOrigin: string;
-    hasVerify: boolean;
-    resultDelivery: "agent" | "endpoint" | "both";
 };
 
 export type MessageMetadata = {
@@ -89,10 +87,7 @@ export type MessageMetadata = {
     isAborted?: boolean;
     tokenUsage?: TokenUsage;
     attachments?: AttachmentSummary[];
-    interactiveTools?: Record<string, InteractiveToolBinding>;
-    /** Per tool call: the trusted reference its initiate call returned. A
-     * verified completion must match it — the browser's word is never enough. */
-    interactiveReferences?: Record<string, string>;
+    clientTools?: Record<string, ClientToolBinding>;
 };
 
 /**
@@ -111,15 +106,32 @@ export type CortexMessage<TPart = unknown> = {
 };
 
 /**
- * Response of `POST /chat/:chatId/tools/:toolCallId/initiate`. `interactive:
- * false` means the pending call is not an interactive CC tool — the widget
+ * Key under the AG-UI request's `forwardedProps` carrying the answers to
+ * parked client tool calls on a continuation request. The server owns the
+ * transcript (a continuation sends `messages: []`), so the answered assistant
+ * message itself never crosses the wire — the SDK's park-boundary snapshot
+ * does not preserve its id, and round-tripping it duplicated the stored
+ * message.
+ */
+export const CLIENT_TOOL_ANSWERS_KEY = "clientToolAnswers";
+
+/** One answered client tool call, applied to the stored transcript server-side. */
+export type ClientToolAnswer = {
+    toolCallId: string;
+    output: unknown;
+    state: "complete" | "error";
+};
+
+/**
+ * Response of `POST /chat/:chatId/tools/:toolCallId/initiate`. `embed:
+ * false` means the pending call is not a CC client tool — the widget
  * falls back to its default rendering for the call. The payload is for the
  * widget only; it never reaches the LLM.
  */
-export type InteractiveInitiateResult =
-    | { interactive: false }
+export type ClientToolInitiateResult =
+    | { embed: false }
     | {
-          interactive: true;
+          embed: true;
           embedUrl: string;
           surface: "inline" | "modal";
           embedOrigin: string;

package/dist/contracts/{graph.d.ts → src/graph/index.d.ts}

@@ -4,11 +4,11 @@
  * with. `@m6d/cortex-server` re-exports all of it, so a project authoring
  * domains still has exactly one import path.
  */
-export type { GraphSchema } from "./graph/schema";
-export { GRAPH_SCHEMA, GRAPH_SCHEMA_VERSION } from "./graph/schema";
-export type { EndpointScalarType, EndpointProperty, ResponseKind, AutoGenerated, ConceptDef, EndpointDef, EndpointInput, ServiceDef, RuleDef, DomainDef, } from "./graph/types";
-export { defineConcept, defineRule, defineService, defineDomain, defineEndpoint, } from "./graph/helpers";
-export type { Neo4jConfig, Neo4jClient } from "./graph/neo4j";
-export { createNeo4jClient } from "./graph/neo4j";
-export type { EmbedFn, EmbeddingProviderConfig } from "./graph/embed";
-export { createEmbedder } from "./graph/embed";
+export type { GraphSchema } from "./schema";
+export { GRAPH_SCHEMA, GRAPH_SCHEMA_VERSION } from "./schema";
+export type { EndpointScalarType, EndpointProperty, ResponseKind, AutoGenerated, ConceptDef, EndpointDef, EndpointInput, ServiceDef, RuleDef, DomainDef, } from "./types";
+export { defineConcept, defineRule, defineService, defineDomain, defineEndpoint } from "./helpers";
+export type { Neo4jConfig, Neo4jClient } from "./clients/neo4j";
+export { createNeo4jClient } from "./clients/neo4j";
+export type { EmbedFn, EmbeddingProviderConfig } from "./clients/embed";
+export { createEmbedder } from "./clients/embed";

package/dist/contracts/{runtime.d.ts → src/runtime/index.d.ts}

@@ -61,23 +61,18 @@ export declare const knowledgeChunkSchema: z.ZodObject<{
     }, z.core.$strip>;
 }, z.core.$strip>;
 /**
- * Runtime contract §5.4: present on signatures of `interactive` tools — flows
+ * Runtime contract §5.4: present on signatures of `embedded` tools — flows
  * the end user completes in an embedded surface inside the chat widget. The
  * tool's endpoint fields act as the *initiate* call (returns the embed URL);
- * `hasVerify` marks a second, server-trusted call that settles the result.
+ * the result the page reports back is relayed as-is — verifying it is the
+ * integrating backend's job.
  */
-export declare const toolInteractionSchema: z.ZodObject<{
+export declare const toolEmbedSchema: z.ZodObject<{
     surface: z.ZodEnum<{
         inline: "inline";
         modal: "modal";
     }>;
     embedOrigin: z.ZodURL;
-    hasVerify: z.ZodBoolean;
-    resultDelivery: z.ZodEnum<{
-        agent: "agent";
-        endpoint: "endpoint";
-        both: "both";
-    }>;
 }, z.core.$strip>;
 export declare const toolSignatureSchema: z.ZodObject<{
     toolId: z.ZodUUID;
@@ -88,18 +83,12 @@ export declare const toolSignatureSchema: z.ZodObject<{
     signature: z.ZodString;
     score: z.ZodNullable<z.ZodNumber>;
     pinned: z.ZodBoolean;
-    interaction: z.ZodOptional<z.ZodObject<{
+    embed: z.ZodOptional<z.ZodObject<{
         surface: z.ZodEnum<{
             inline: "inline";
             modal: "modal";
         }>;
         embedOrigin: z.ZodURL;
-        hasVerify: z.ZodBoolean;
-        resultDelivery: z.ZodEnum<{
-            agent: "agent";
-            endpoint: "endpoint";
-            both: "both";
-        }>;
     }, z.core.$strip>>;
     inputSchema: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
 }, z.core.$strip>;
@@ -185,18 +174,12 @@ export declare const resolveResponseSchema: z.ZodObject<{
         signature: z.ZodString;
         score: z.ZodNullable<z.ZodNumber>;
         pinned: z.ZodBoolean;
-        interaction: z.ZodOptional<z.ZodObject<{
+        embed: z.ZodOptional<z.ZodObject<{
             surface: z.ZodEnum<{
                 inline: "inline";
                 modal: "modal";
             }>;
             embedOrigin: z.ZodURL;
-            hasVerify: z.ZodBoolean;
-            resultDelivery: z.ZodEnum<{
-                agent: "agent";
-                endpoint: "endpoint";
-                both: "both";
-            }>;
         }, z.core.$strip>>;
         inputSchema: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
     }, z.core.$strip>>;
@@ -238,18 +221,12 @@ export declare const searchToolsResponseSchema: z.ZodObject<{
         signature: z.ZodString;
         score: z.ZodNullable<z.ZodNumber>;
         pinned: z.ZodBoolean;
-        interaction: z.ZodOptional<z.ZodObject<{
+        embed: z.ZodOptional<z.ZodObject<{
             surface: z.ZodEnum<{
                 inline: "inline";
                 modal: "modal";
             }>;
             embedOrigin: z.ZodURL;
-            hasVerify: z.ZodBoolean;
-            resultDelivery: z.ZodEnum<{
-                agent: "agent";
-                endpoint: "endpoint";
-                both: "both";
-            }>;
         }, z.core.$strip>>;
         inputSchema: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
     }, z.core.$strip>>;
@@ -276,18 +253,12 @@ export declare const searchServicesResponseSchema: z.ZodObject<{
         signature: z.ZodString;
         score: z.ZodNullable<z.ZodNumber>;
         pinned: z.ZodBoolean;
-        interaction: z.ZodOptional<z.ZodObject<{
+        embed: z.ZodOptional<z.ZodObject<{
             surface: z.ZodEnum<{
                 inline: "inline";
                 modal: "modal";
             }>;
             embedOrigin: z.ZodURL;
-            hasVerify: z.ZodBoolean;
-            resultDelivery: z.ZodEnum<{
-                agent: "agent";
-                endpoint: "endpoint";
-                both: "both";
-            }>;
         }, z.core.$strip>>;
         inputSchema: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
     }, z.core.$strip>>;
@@ -314,10 +285,6 @@ export declare const searchKnowledgeResponseSchema: z.ZodObject<{
 }, z.core.$strip>;
 export declare const executeRequestSchema: z.ZodObject<{
     input: z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    phase: z.ZodOptional<z.ZodEnum<{
-        verify: "verify";
-        initiate: "initiate";
-    }>>;
     context: z.ZodOptional<z.ZodObject<{
         threadId: z.ZodOptional<z.ZodString>;
         userId: z.ZodOptional<z.ZodString>;
@@ -381,7 +348,7 @@ export declare const runtimeErrorSchema: z.ZodObject<{
         upstreamStatus: z.ZodOptional<z.ZodNumber>;
     }, z.core.$strip>;
 }, z.core.$strip>;
-export type ToolInteraction = z.infer<typeof toolInteractionSchema>;
+export type ToolEmbed = z.infer<typeof toolEmbedSchema>;
 export type RuntimeAgentConfig = z.infer<typeof runtimeAgentConfigSchema>;
 export type ResolveRequest = z.input<typeof resolveRequestSchema>;
 export type ResolveResponse = z.infer<typeof resolveResponseSchema>;

package/dist/contracts/{wire.d.ts → src/wire/index.d.ts}

@@ -51,16 +51,14 @@ export type TokenUsage = {
     total: number;
 };
 /**
- * How to launch one interactive tool: stamped by the server, per tool name, on
+ * How to launch one client tool: stamped by the server, per tool name, on
  * the metadata of an assistant message that may carry its pending call. Kept in
  * the message so the binding survives server restarts while a run is parked.
  */
-export type InteractiveToolBinding = {
+export type ClientToolBinding = {
     toolId: string;
     surface: "inline" | "modal";
     embedOrigin: string;
-    hasVerify: boolean;
-    resultDelivery: "agent" | "endpoint" | "both";
 };
 export type MessageMetadata = {
     modelId?: string;
@@ -68,10 +66,7 @@ export type MessageMetadata = {
     isAborted?: boolean;
     tokenUsage?: TokenUsage;
     attachments?: AttachmentSummary[];
-    interactiveTools?: Record<string, InteractiveToolBinding>;
-    /** Per tool call: the trusted reference its initiate call returned. A
-     * verified completion must match it — the browser's word is never enough. */
-    interactiveReferences?: Record<string, string>;
+    clientTools?: Record<string, ClientToolBinding>;
 };
 /**
  * A stored message as it is persisted and served. TanStack AI's `UIMessage`
@@ -88,15 +83,30 @@ export type CortexMessage<TPart = unknown> = {
     metadata?: MessageMetadata;
 };
 /**
- * Response of `POST /chat/:chatId/tools/:toolCallId/initiate`. `interactive:
- * false` means the pending call is not an interactive CC tool — the widget
+ * Key under the AG-UI request's `forwardedProps` carrying the answers to
+ * parked client tool calls on a continuation request. The server owns the
+ * transcript (a continuation sends `messages: []`), so the answered assistant
+ * message itself never crosses the wire — the SDK's park-boundary snapshot
+ * does not preserve its id, and round-tripping it duplicated the stored
+ * message.
+ */
+export declare const CLIENT_TOOL_ANSWERS_KEY = "clientToolAnswers";
+/** One answered client tool call, applied to the stored transcript server-side. */
+export type ClientToolAnswer = {
+    toolCallId: string;
+    output: unknown;
+    state: "complete" | "error";
+};
+/**
+ * Response of `POST /chat/:chatId/tools/:toolCallId/initiate`. `embed:
+ * false` means the pending call is not a CC client tool — the widget
  * falls back to its default rendering for the call. The payload is for the
  * widget only; it never reaches the LLM.
  */
-export type InteractiveInitiateResult = {
-    interactive: false;
+export type ClientToolInitiateResult = {
+    embed: false;
 } | {
-    interactive: true;
+    embed: true;
     embedUrl: string;
     surface: "inline" | "modal";
     embedOrigin: string;

package/dist/src/lib/adapters/database/index.d.ts

@@ -34,13 +34,6 @@ export type DatabaseAdapter = {
         upsert(threadId: string, messages: ChatMessage[], options?: {
             replaceAttachments?: boolean;
         }): Promise<void>;
-        /**
-         * Atomically merges one anchored interactive reference into the
-         * message's metadata as a single-statement JSON merge — safe under
-         * concurrent writers across replicas, unlike a read-modify-write of
-         * the whole message.
-         */
-        mergeInteractiveReference(threadId: string, messageId: string, toolCallId: string, reference: string): Promise<void>;
     };
     llmRequests: {
         insert(requests: {

package/dist/src/lib/adapters/database/message-content.d.ts

@@ -16,8 +16,7 @@ export declare function withOwnedAttachments(messages: ChatMessage[], replaceAtt
         providerMetadata?: unknown;
         isAborted?: boolean;
         tokenUsage?: import("../../types").TokenUsage;
-        interactiveTools?: Record<string, import("../..").InteractiveToolBinding>;
-        interactiveReferences?: Record<string, string>;
+        clientTools?: Record<string, import("../..").ClientToolBinding>;
     };
     id: string;
     role: "system" | "user" | "assistant";

package/dist/src/lib/adapters/database/mssql/index.d.ts

@@ -76,7 +76,6 @@ export declare function createMssqlAdapter(connectionString: string, storage?: S
         upsert(threadId: string, messagesToUpsert: import("../../../types").ChatMessage[], options?: {
             replaceAttachments?: boolean;
         }): Promise<void>;
-        mergeInteractiveReference(threadId: string, messageId: string, toolCallId: string, reference: string): Promise<void>;
     };
     llmRequests: {
         insert(requests: {

package/dist/src/lib/adapters/database/mssql/messages.d.ts

@@ -34,5 +34,4 @@ export declare function createMessagesRepository(db: MssqlDb): {
     upsert(threadId: string, messagesToUpsert: ChatMessage[], options?: {
         replaceAttachments?: boolean;
     }): Promise<void>;
-    mergeInteractiveReference(threadId: string, messageId: string, toolCallId: string, reference: string): Promise<void>;
 };

package/dist/src/lib/adapters/database/postgres/index.d.ts

@@ -76,7 +76,6 @@ export declare function createPostgresAdapter(connectionString: string, storage?
         upsert(threadId: string, messagesToUpsert: import("../../../types").ChatMessage[], options?: {
             replaceAttachments?: boolean;
         }): Promise<void>;
-        mergeInteractiveReference(threadId: string, messageId: string, toolCallId: string, reference: string): Promise<void>;
     };
     llmRequests: {
         insert(requests: {

package/dist/src/lib/adapters/database/postgres/messages.d.ts

@@ -34,5 +34,4 @@ export declare function createMessagesRepository(db: PostgresDb): {
     upsert(threadId: string, messagesToUpsert: ChatMessage[], options?: {
         replaceAttachments?: boolean;
     }): Promise<void>;
-    mergeInteractiveReference(threadId: string, messageId: string, toolCallId: string, reference: string): Promise<void>;
 };

package/dist/src/lib/ai/cc-runtime.d.ts

@@ -1,7 +1,7 @@
 import type { ResolvedCortexAgentConfig } from "../config";
 import type { Thread } from "../types";
 import type { ControlCenterClient } from "../cc/client";
-import type { CcInteractiveTool, CcToolRegistry } from "../cc/registry";
+import type { CcClientTool, CcToolRegistry } from "../cc/registry";
 import type { ResolveResponse, RuntimeAgentConfig } from "../cc/types";
 type CcRuntimeOptions = {
     ccClient: ControlCenterClient | null;
@@ -48,7 +48,7 @@ export declare function createCcRuntime(options: CcRuntimeOptions): {
         publishedAt: string;
     };
     registry: CcToolRegistry;
-    interactiveTools: Map<string, CcInteractiveTool>;
+    clientTools: Map<string, CcClientTool>;
     threadId: string;
     turnKey: string;
     userId: string;