@mastra/client-js 1.13.2 → 1.13.3-alpha.1

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # @mastra/client-js
 
+## 1.13.3-alpha.1
+
+### Patch Changes
+
+- Updated dependencies [[`3db852b`](https://github.com/mastra-ai/mastra/commit/3db852bff74e29f60d415a7b0f1583d6ce2bad92)]:
+  - @mastra/core@1.24.1-alpha.1
+
+## 1.13.3-alpha.0
+
+### Patch Changes
+
+- Updated dependencies [[`ef94400`](https://github.com/mastra-ai/mastra/commit/ef9440049402596b31f2ab976c5e4508f6cb6c91)]:
+  - @mastra/core@1.24.1-alpha.0
+
 ## 1.13.2
 
 ### Patch Changes

package/dist/docs/SKILL.md

@@ -3,7 +3,7 @@ name: mastra-client-js
 description: Documentation for @mastra/client-js. Use when working with @mastra/client-js APIs, configuration, or implementation.
 metadata:
   package: "@mastra/client-js"
-  version: "1.13.2"
+  version: "1.13.3-alpha.1"
 ---
 
 ## When to use

package/dist/docs/assets/SOURCE_MAP.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.13.2",
+  "version": "1.13.3-alpha.1",
   "package": "@mastra/client-js",
   "exports": {},
   "modules": {}

package/dist/docs/references/docs-editor-overview.md

@@ -72,6 +72,72 @@ Go to the **Agents** tab in Studio and select an agent to edit. Select the **Edi
 
 Modify the system prompt and save a new draft version. Afterwards, publish the draft to make it the active version.
 
+## Programmatic control
+
+Everything you can do in Studio is also available programmatically through [`mastra.getEditor()`](https://mastra.ai/reference/core/getEditor). This is useful for scripting bulk updates, seeding stored configurations from code, or building automation that tunes agents based on evaluation results.
+
+Call `mastra.getEditor()` from anywhere you have access to the `Mastra` instance. It returns the `MastraEditor` instance you registered, with namespaces for each resource type:
+
+```typescript
+import { mastra } from '../mastra'
+
+const editor = mastra.getEditor()
+if (!editor) throw new Error('Editor is not registered on Mastra')
+
+// Create a stored agent override for an existing code-defined agent
+await editor.agent.create({
+  id: 'support-agent',
+  instructions: 'You are a friendly support agent for Acme Inc.',
+  tools: {
+    search_kb: { description: 'Search the Acme knowledge base' },
+  },
+})
+```
+
+Use `editor.agent.update()` to change an existing stored configuration. Every update creates a new draft version automatically:
+
+```typescript
+import { mastra } from '../mastra'
+
+const editor = mastra.getEditor()!
+
+await editor.agent.update({
+  id: 'support-agent',
+  instructions:
+    "You are a friendly support agent for Acme Inc. Always respond in the user's language.",
+})
+```
+
+The `editor.agent` namespace also exposes `getById`, `list`, `listResolved`, and `delete`. The `editor.prompt` namespace exposes the same CRUD methods for prompt blocks. See [Prompts](https://mastra.ai/docs/editor/prompts) for examples.
+
+### Server endpoints
+
+The same operations are available over HTTP through the Mastra server. Use these when you want to manage stored agents from a separate service or from a non-TypeScript client:
+
+| Method   | Path                            | Description               |
+| -------- | ------------------------------- | ------------------------- |
+| `GET`    | `/stored/agents`                | List all stored agents.   |
+| `POST`   | `/stored/agents`                | Create a stored agent.    |
+| `GET`    | `/stored/agents/:storedAgentId` | Get a stored agent by ID. |
+| `PATCH`  | `/stored/agents/:storedAgentId` | Update a stored agent.    |
+| `DELETE` | `/stored/agents/:storedAgentId` | Delete a stored agent.    |
+
+The Client SDK wraps these endpoints with `client.listStoredAgents()`, `client.createStoredAgent()`, and `client.getStoredAgent()`. Version management endpoints live under `/stored/agents/:storedAgentId/versions`, see [version management](https://mastra.ai/reference/client-js/agents) for the full list.
+
+### Automated experimentation
+
+Because stored agents are just data, you can build automation loops that tune agents without human involvement. A common pattern is to pair the editor API with [datasets](https://mastra.ai/docs/evals/datasets/overview) and [experiments](https://mastra.ai/docs/evals/datasets/running-experiments):
+
+- Run a dataset through the current version of an agent and score the results.
+- Have another agent read the failing cases and propose changes to the instructions or tools.
+- Apply those changes with `editor.agent.update()` to create a new draft.
+- Re-run the experiment against the draft and compare scores to the baseline.
+- Promote the draft to the published version when the scores improve.
+
+This turns agent tuning into a closed feedback loop. One agent owns the production configuration, another agent iterates on it, and every change is versioned so you can roll back if a round of automated edits makes things worse. Combine this with [version targeting](#version-targeting-and-experimentation) to keep production traffic on the published version while the draft is being tested.
+
+> **Note:** See the [MastraEditor reference](https://mastra.ai/reference/editor/mastra-editor) for the full namespace API.
+
 ## What can be overridden
 
 When you edit a code-defined agent through the editor, only specific fields can be changed:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/client-js",
-  "version": "1.13.2",
+  "version": "1.13.3-alpha.1",
   "description": "The official TypeScript library for the Mastra Client API",
   "author": "",
   "type": "module",
@@ -37,8 +37,8 @@
     "@ai-sdk/ui-utils": "^1.2.11",
     "@lukeed/uuid": "^2.0.1",
     "json-schema": "^0.4.0",
-    "@mastra/schema-compat": "1.2.7",
-    "@mastra/core": "1.24.0"
+    "@mastra/core": "1.24.1-alpha.1",
+    "@mastra/schema-compat": "1.2.7"
   },
   "peerDependencies": {
     "zod": "^3.25.0 || ^4.0.0"
@@ -53,10 +53,10 @@
     "typescript": "^5.9.3",
     "vitest": "4.0.18",
     "zod": "^4.3.6",
-    "@internal/ai-sdk-v4": "0.0.28",
-    "@internal/types-builder": "0.0.56",
     "@internal/ai-sdk-v5": "0.0.28",
-    "@internal/lint": "0.0.81"
+    "@internal/ai-sdk-v4": "0.0.28",
+    "@internal/lint": "0.0.81",
+    "@internal/types-builder": "0.0.56"
   },
   "engines": {
     "node": ">=22.13.0"