@mastra/client-js 1.53.0-alpha.6 → 1.53.0-alpha.7
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/dist/docs/SKILL.md
CHANGED
|
@@ -3,7 +3,7 @@ name: mastra-client-js
|
|
|
3
3
|
description: Documentation for @mastra/client-js. Use when working with @mastra/client-js APIs, configuration, or implementation.
|
|
4
4
|
metadata:
|
|
5
5
|
package: "@mastra/client-js"
|
|
6
|
-
version: "1.53.0-alpha.
|
|
6
|
+
version: "1.53.0-alpha.7"
|
|
7
7
|
---
|
|
8
8
|
|
|
9
9
|
## When to use
|
|
@@ -50,7 +50,7 @@ When the thread has a running agent stream, `sendMessage()` becomes new input in
|
|
|
50
50
|
|
|
51
51
|
### Input during reasoning
|
|
52
52
|
|
|
53
|
-
In the default
|
|
53
|
+
In the default loop and experimental durable and evented agents, accepted pending messages and signals interrupt a model request that has produced only reasoning or metadata. This includes the wait for its first token. Mastra cancels that request, discards its response from model history and memory, and includes queued input in the next request within the same run. Earlier completed responses stay in history.
|
|
54
54
|
|
|
55
55
|
Once text, tool calls, or other response content starts, signals wait for the next loop boundary. Running tools aren't cancelled or repeated. If the run reaches `maxSteps`, queued input may be saved without a response. `queueMessage()` still waits for the active run to finish. Signals that processors write directly to the message history don't interrupt their own request.
|
|
56
56
|
|
|
@@ -58,7 +58,7 @@ Interrupted requests don't count toward `maxSteps` or advance `stepNumber`. The
|
|
|
58
58
|
|
|
59
59
|
Already-streamed reasoning may remain visible until the client reloads history. When input arrives while per-step input processors (`processInputStep`) run, the processors finish and Mastra cancels the model request they prepared. Custom output processors also keep running after a cancellation, and the next request waits for their in-flight work to settle. Mastra discards framework-owned response buffers, but doesn't undo processor state, data that processors write while the cancelled request settles, or external side effects. Usage totals exclude interrupted requests, including any usage the provider reports for them. Providers may still bill for those requests.
|
|
60
60
|
|
|
61
|
-
|
|
61
|
+
Reasoning interruption doesn't apply to the Inngest engine, or to durable and evented steps that run in a different process from the one that accepted the input.
|
|
62
62
|
|
|
63
63
|
## Message input
|
|
64
64
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mastra/client-js",
|
|
3
|
-
"version": "1.53.0-alpha.
|
|
3
|
+
"version": "1.53.0-alpha.7",
|
|
4
4
|
"description": "The official TypeScript library for the Mastra Client API",
|
|
5
5
|
"author": "",
|
|
6
6
|
"type": "module",
|
|
@@ -38,7 +38,7 @@
|
|
|
38
38
|
"canonicalize": "^1.0.8",
|
|
39
39
|
"jose": "^6.2.11",
|
|
40
40
|
"json-schema": "^0.4.0",
|
|
41
|
-
"@mastra/core": "1.76.0-alpha.
|
|
41
|
+
"@mastra/core": "1.76.0-alpha.7",
|
|
42
42
|
"@mastra/schema-compat": "1.3.13"
|
|
43
43
|
},
|
|
44
44
|
"peerDependencies": {
|
|
@@ -55,10 +55,10 @@
|
|
|
55
55
|
"typescript": "^7.0.2",
|
|
56
56
|
"vitest": "4.1.11",
|
|
57
57
|
"zod": "^4.6.4",
|
|
58
|
-
"@internal/ai-sdk-v5": "0.0.88",
|
|
59
58
|
"@internal/ai-sdk-v4": "0.0.88",
|
|
60
|
-
"@internal/
|
|
61
|
-
"@internal/types-builder": "0.0.116"
|
|
59
|
+
"@internal/ai-sdk-v5": "0.0.88",
|
|
60
|
+
"@internal/types-builder": "0.0.116",
|
|
61
|
+
"@internal/lint": "0.0.141"
|
|
62
62
|
},
|
|
63
63
|
"engines": {
|
|
64
64
|
"node": ">=22.13.0"
|