@poncho-ai/sdk 1.10.0 → 1.11.0

package/.turbo/turbo-build.log

@@ -1,5 +1,5 @@
 
-> @poncho-ai/sdk@1.10.0 build /home/runner/work/poncho-ai/poncho-ai/packages/sdk
+> @poncho-ai/sdk@1.11.0 build /home/runner/work/poncho-ai/poncho-ai/packages/sdk
 > tsup src/index.ts --format esm --dts
 
 CLI Building entry: src/index.ts
@@ -10,5 +10,5 @@
 ESM dist/index.js 17.24 KB
 ESM ⚡️ Build success in 21ms
 DTS Build start
-DTS ⚡️ Build success in 1318ms
-DTS dist/index.d.ts 28.29 KB
+DTS ⚡️ Build success in 1385ms
+DTS dist/index.d.ts 29.09 KB

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # @poncho-ai/sdk
 
+## 1.11.0
+
+### Minor Changes
+
+- [`1adaae2`](https://github.com/cesr/poncho-ai/commit/1adaae2d4cc55800f01d602f2a7d6ecc65031443) Thanks [@cesr](https://github.com/cesr)! - harness: device-dispatch mode for tools that execute on a connected client
+
+  Tools can now be marked `dispatch: "device"` on `loadedConfig.tools`. When
+  the model calls such a tool the dispatcher pauses the run, emits a new
+  `tool:device:required` event, and checkpoints with the new
+  `kind: "device"` discriminator on `pendingApprovals` — same plumbing as
+  the approval flow, different trigger and different resume payload.
+  Consumers (e.g. PonchOS for iOS device tools) drive the external
+  execution and feed the result back via `continueFromToolResult`.
+
+  Approval can be combined: `{access: "approval", dispatch: "device"}`
+  yields the approval card first, then on resume falls through to the
+  device-required event. The wire vocabulary for approvals
+  (`approvalId` etc.) is unchanged; the `pendingApprovals` column /
+  field name stays.
+
+  `ToolAccess` is broadened to accept both the legacy string `"approval"`
+  and the new `{access?, dispatch?}` object form. Existing configs keep
+  working unchanged.
+
 ## 1.10.0
 
 ### Minor Changes

package/dist/index.d.ts

@@ -858,6 +858,32 @@ type AgentEvent = {
         name: string;
         input: Record<string, unknown>;
     }>;
+} | {
+    /**
+     * Tool wants to execute on a connected client device (e.g. iOS).
+     * The consumer of the harness is responsible for routing this event
+     * to the appropriate WebSocket and POSTing the tool's result back via
+     * `resumeRunFromCheckpoint`. Carries the same envelope as the
+     * approval-required event; `requestId` plays the role of `approvalId`.
+     */
+    type: "tool:device:required";
+    tool: string;
+    input: unknown;
+    requestId: string;
+} | {
+    type: "tool:device:checkpoint";
+    approvals: Array<{
+        approvalId: string;
+        tool: string;
+        toolCallId: string;
+        input: Record<string, unknown>;
+    }>;
+    checkpointMessages: Message[];
+    pendingToolCalls: Array<{
+        id: string;
+        name: string;
+        input: Record<string, unknown>;
+    }>;
 } | {
     type: "browser:frame";
     data: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@poncho-ai/sdk",
-  "version": "1.10.0",
+  "version": "1.11.0",
   "description": "Core types and utilities for building Poncho skills",
   "repository": {
     "type": "git",

package/src/index.ts

@@ -196,6 +196,30 @@ export type AgentEvent =
       checkpointMessages: Message[];
       pendingToolCalls: Array<{ id: string; name: string; input: Record<string, unknown> }>;
     }
+  | {
+      /**
+       * Tool wants to execute on a connected client device (e.g. iOS).
+       * The consumer of the harness is responsible for routing this event
+       * to the appropriate WebSocket and POSTing the tool's result back via
+       * `resumeRunFromCheckpoint`. Carries the same envelope as the
+       * approval-required event; `requestId` plays the role of `approvalId`.
+       */
+      type: "tool:device:required";
+      tool: string;
+      input: unknown;
+      requestId: string;
+    }
+  | {
+      type: "tool:device:checkpoint";
+      approvals: Array<{
+        approvalId: string;
+        tool: string;
+        toolCallId: string;
+        input: Record<string, unknown>;
+      }>;
+      checkpointMessages: Message[];
+      pendingToolCalls: Array<{ id: string; name: string; input: Record<string, unknown> }>;
+    }
   | { type: "browser:frame"; data: string; width: number; height: number }
   | {
       type: "browser:status";