@commonlyai/mcp 0.3.19 → 0.3.20

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@commonlyai/mcp",
   "mcpName": "io.github.Team-Commonly/commonly",
-  "version": "0.3.19",
+  "version": "0.3.20",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",

package/src/tools.js

@@ -215,6 +215,22 @@ export const buildTools = (config) => {
         body: outcome === undefined ? undefined : { outcome },
       })),
     },
+    {
+      name: 'commonly_checkpoint_event',
+      description: 'Checkpoint ONE inbox event only after tool-side work is committed (including a reply posted through a tool), or a deliberate NO_REPLY. Never checkpoint an answer held for final CLI output: the wrapper must post that reply before acknowledging the item. This durably acknowledges that event now, so a later turn timeout does not replay it. Use only the eventId and deliveryId supplied together in the current inbox item. Never checkpoint unseen or unfinished work. Release any message claim with its correct completed/declined outcome first. A failed call is not a checkpoint; leave the item pending. This posts no chat message and does not complete a task.',
+      inputSchema: reqWith({ eventId: { type: 'string', minLength: 1 }, deliveryId: { type: 'string', minLength: 1 } }, ['eventId', 'deliveryId']),
+      call: wrap(async ({ eventId, deliveryId }) => {
+        if (typeof eventId !== 'string' || !eventId.trim()
+          || typeof deliveryId !== 'string' || !deliveryId.trim()) {
+          throw new Error('eventId and deliveryId from the current inbox item are required');
+        }
+        return request(config, {
+          method: 'POST',
+          path: `/api/agents/runtime/events/${encodeURIComponent(eventId)}/ack`,
+          body: { deliveryId, result: { outcome: 'acknowledged', reason: 'handled-checkpoint' } },
+        });
+      }),
+    },
     {
       name: 'commonly_get_messages',
       description: 'Read chat messages from a pod. `limit` is clamped server-side to [1, 50] (default 20). To page into older history, pass the `createdAt` timestamp of the oldest message as `before`; the response `hasMore` flag distinguishes another page from the end of history. Pass `threadRootId` (a message id) to read one thread — returns the root message plus every reply in that thread, oldest first.',