@2kw/ai-mcp-server 8.0.0-dev.5 → 8.0.1

package/dist/lib/agent-run.d.ts

@@ -65,6 +65,18 @@ export interface PendingInput {
     mode: InputMode;
     answerUrl: string;
 }
+/**
+ * A table or chart the agent showed the user (#1419): a `backbone:ui` item, its validated `props` as the
+ * server sent them. A client renders from `props`, never from the call's arguments.
+ */
+export interface ShownComponent {
+    id: string;
+    callId: string;
+    /** `table` or `chart`; another value is a component this build does not know. */
+    component: string;
+    schemaVersion: number;
+    props: unknown;
+}
 /** The end user's conversation mode (epic &59); the server matches these three values exactly. */
 export type ConversationMode = "plan" | "ask" | "auto";
 export declare const CONVERSATION_MODES: readonly ConversationMode[];
@@ -97,6 +109,7 @@ export interface RunEnvelope {
     pendingToolCalls: PendingToolCall[];
     pendingConnections: PendingConnection[];
     pendingInputs: PendingInput[];
+    components: ShownComponent[];
     incompleteReason: string | null;
     usage: {
         inputTokens: number;

package/dist/lib/agent-run.js

@@ -108,6 +108,8 @@ const DECODED_ITEM_TYPES = new Set([
     "backbone:connector_auth_request",
     "backbone:input_request",
     "backbone:tool_image",
+    // A table or chart a finished ShowTable or ShowChart call showed (#1419): it never holds a run either.
+    "backbone:ui",
     "mcp_approval_request",
     "mcp_call",
     "mcp_list_tools",
@@ -302,6 +304,15 @@ export function buildRunEnvelope(result, agentRef, chatUrl = DEFAULT_CHAT_URL) {
         pendingToolCalls,
         pendingConnections,
         pendingInputs,
+        components: output
+            .filter((i) => i.type === "backbone:ui")
+            .map((i) => ({
+            id: String(i.id),
+            callId: String(i.call_id),
+            component: String(i.component),
+            schemaVersion: Number(i.schema_version),
+            props: i.props ?? null,
+        })),
         incompleteReason: result?.incomplete_details?.reason ?? null,
         usage: result?.usage
             ? { inputTokens: result.usage.input_tokens ?? 0, outputTokens: result.usage.output_tokens ?? 0 }

package/dist/tools/ai-gateway.js

@@ -100,7 +100,7 @@ export function register(server, client) {
         return input === "" ? [] : input;
     };
     // ── create_response ─────────────────────────────────────────────────────
-    server.tool("2kw_create_response", "Send a request through Backbone's OpenAI-compatible OpenResponses endpoint (POST /v1/responses). Model format: 'provider/model' for a direct gateway call via `model`, or use `agent` to invoke a stored agent by id or name (optionally 'ref@label', e.g. 'support-bot@latest'). With `agent`, `agentModel` runs this one request on another model from the agent version's `models` list. With `agent`, the reply is the run envelope as JSON (status, text, tool calls, pending approvals, response id, next step) followed by the model that answered; answer an approval pause with 2kw_decide_agent_approvals. A run paused on a relayed (client-side) tool call comes back with status requires_tool_output and `pendingToolCalls`; answer it with 2kw_decide_agent_approvals `outputs`. A run that needs the user's own sign-in to a connector pauses with status requires_tool_output and `pendingConnections` (label, host, reason): no tool here can answer that; tell the user to connect it in chat.2kw.ai → Connectors, as the envelope's `next` says; once they have, resume it with 2kw_create_response `previousResponseId` (and an empty `input`). A run where a connector asks the user a question pauses with status requires_tool_output and `pendingInputs` (label, tool, mode, answerUrl): the user answers it in chat at `answerUrl`, not here. Always non-streaming. " + MODE_RULE, {
+    server.tool("2kw_create_response", "Send a request through Backbone's OpenAI-compatible OpenResponses endpoint (POST /v1/responses). Model format: 'provider/model' for a direct gateway call via `model`, or use `agent` to invoke a stored agent by id or name (optionally 'ref@label', e.g. 'support-bot@latest'). With `agent`, `agentModel` runs this one request on another model from the agent version's `models` list. With `agent`, the reply is the run envelope as JSON (status, text, tool calls, pending approvals, the tables and charts the agent showed the user as `components`, response id, next step) followed by the model that answered; answer an approval pause with 2kw_decide_agent_approvals. A run paused on a relayed (client-side) tool call comes back with status requires_tool_output and `pendingToolCalls`; answer it with 2kw_decide_agent_approvals `outputs`. A run that needs the user's own sign-in to a connector pauses with status requires_tool_output and `pendingConnections` (label, host, reason): no tool here can answer that; tell the user to connect it in chat.2kw.ai → Connectors, as the envelope's `next` says; once they have, resume it with 2kw_create_response `previousResponseId` (and an empty `input`). A run where a connector asks the user a question pauses with status requires_tool_output and `pendingInputs` (label, tool, mode, answerUrl): the user answers it in chat at `answerUrl`, not here. Always non-streaming. " + MODE_RULE, {
         input: z
             .string()
             .describe("The input text (sent as a single user message). May be empty only with `previousResponseId`, to resume a paused response without a new message."),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@2kw/ai-mcp-server",
-  "version": "8.0.0-dev.5",
+  "version": "8.0.1",
   "description": "MCP server for 2kw.ai — EU-hosted AI platform: OpenAI-compatible LLM gateway, schema-driven document extraction, transcription, agents with a knowledge base, and cost observability. 199 tools for Claude Code, Cursor, and Windsurf.",
   "mcpName": "ai.2kw/mcp-server",
   "keywords": [