@vellumai/plugin-api 0.11.2-dev.202608052357.8f326c2 → 0.11.2-dev.202608060040.fd8f444

package/index.d.ts

@@ -6138,12 +6138,32 @@ export declare interface SendMessageConfig {
      */
     logit_bias?: Record<string, number>;
     /**
-     * When true, the most recent user message's content varies across
-     * otherwise-identical turns (e.g. a per-turn memory block was injected into
-     * it). The provider places the primary long-TTL cache breakpoint on the most
-     * recent *stable* user message instead of the volatile latest one, so the
-     * cached prefix stays reusable across turns. Default false — existing
-     * behavior.
+     * When true, the TURN-STARTING user message carries content that will not
+     * recur byte-identically on the next turn, so a long-TTL breakpoint placed
+     * on it could never be read back across turns. The agent loop is the only
+     * producer: it sets the flag from the history it is about to send, when the
+     * turn-starting message carries a memory-v3 `<memory_spotlight>` block (the
+     * one injected block strip-and-replaced from every user message each turn).
+     *
+     * The flag describes the turn, not the request, so it holds for every
+     * request the turn makes, including tool-loop iterations, whose trailing
+     * tool-result message is user-role but carries no injected blocks.
+     *
+     * Consumed by the Anthropic client only, where it selects the TTL of the
+     * turn-start breakpoint: short instead of long. The block is still marked,
+     * so the turn's tool-loop iterations read the prefix back and each hit
+     * refreshes the entry; nothing is spent on a long-TTL entry whose bytes
+     * change before the next turn could reach it. Holding the flag steady across
+     * the turn is what keeps that one boundary on a single TTL; marking it at
+     * two would bill two writes for one reusable prefix.
+     *
+     * The OpenAI Responses transport ignores the flag and marks every markable
+     * user item: a volatile message is fixed within its own turn, so the write is
+     * prepaid once and read back by each tool-loop iteration.
+     *
+     * Default false. Providers that place no message-level breakpoints, or that
+     * key their cache on a request-level identifier rather than message bytes,
+     * can ignore it.
      */
     mutableLatestUserMessage?: boolean;
     /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vellumai/plugin-api",
-  "version": "0.11.2-dev.202608052357.8f326c2",
+  "version": "0.11.2-dev.202608060040.fd8f444",
   "description": "Public TypeScript authoring contract for Vellum assistant plugins.",
   "license": "MIT",
   "type": "module",