@foldkit/devtools-mcp 0.13.3 → 0.14.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -12,7 +12,7 @@ With it attached, agents can:
12
12
  - Inspect runtime state: current index, retained history bounds, pause status
13
13
  - Replay to any past state and resume
14
14
  - Discover the runtime's `Message` Schema as JSON Schema so agents can construct valid payloads without reading the application source
15
- - Dispatch Messages into the runtime, decoded against your `Message` Schema
15
+ - Dispatch Messages into the runtime, singly or as an ordered batch, decoded against your `Message` Schema
16
16
 
17
17
  ## Quick Start
18
18
 
@@ -85,6 +85,7 @@ Each tool accepts an optional `runtime_id`. When omitted, the most recently conn
85
85
  | `foldkit_resume` | Resumes normal execution after a replay. |
86
86
  | `foldkit_get_message_schema` | Describes the runtime's Message Schema so agents can construct valid Messages without reading the application source. With no arguments, returns a small variant index (top-level tag names plus payload fields). With `variant_tag` set to a dot-separated path of variant tags (e.g. `"GotChildMessage.Opened"`), narrows the JSON Schema along the chain and collapses deeper unions to summary placeholders. Returns `maybeResult: None` when the runtime hasn't configured `DevToolsConfig.Message`. |
87
87
  | `foldkit_dispatch_message` | Dispatches a Message into the runtime as if your application produced it. The runtime decodes the payload against your Schema and returns a clean error if it does not match. |
88
+ | `foldkit_dispatch_messages` | Dispatches an ordered batch of 1 to 100 Messages in one call, first to last. The runtime validates every payload before dispatching any of them, so one invalid entry rejects the whole batch with its zero-based position and nothing is dispatched. The response reports the predicted history index for each Message. |
88
89
 
89
90
  ### Reading the Model efficiently
90
91