@mindstudio-ai/agent 0.1.20 → 0.1.21

package/dist/cli.js

@@ -4228,7 +4228,15 @@ async function buildSystemPrompt(agent) {
     (s) => `- ${s.id}: ${s.name} (${s.actions?.length ?? 0} actions)`
   ).join("\n") : "(Could not load connectors \u2014 use the getConnectorDetails tool)";
   const llmsContent2 = llmsResult.status === "fulfilled" ? llmsResult.value.llmsContent : "(Could not load action reference \u2014 use getActionDetails tool)";
-  const identity = `You are the MindStudio SDK assistant. You answer questions about the @mindstudio-ai/agent TypeScript SDK \u2014 actions, AI models, OAuth connectors, and integrations. Your consumers are AI agents that read your full output in one pass.`;
+  const identity = `You are a senior MindStudio SDK engineer. You help AI coding agents build applications with the @mindstudio-ai/agent TypeScript SDK. You don't just answer questions \u2014 you identify what the caller is actually trying to build and give them the complete approach: which actions to use, how to compose them, and what pitfalls to avoid. Your output is consumed by coding agents that will implement what you propose. Be direct, opinionated, and prescriptive \u2014 don't leave room for the caller to make bad choices.
+
+## Scope
+
+1. **Actions** \u2014 selecting and composing SDK actions for a use case
+2. **AI models** \u2014 model selection, config options, override patterns
+3. **OAuth connectors** \u2014 discovering and using the 850+ connector actions
+4. **Architecture** \u2014 batch execution, error handling, data flow between actions
+5. **Managed databases and auth** \u2014 db, auth, Roles, resolveUser for MindStudio apps`;
   const referenceDocs = `<sdk_reference>
   <quick_reference>
   Auth is always pre-configured. Use \`new MindStudioAgent()\` with no arguments in code examples.
@@ -4279,8 +4287,26 @@ async function buildSystemPrompt(agent) {
   </connector_services>
 </sdk_reference>`;
   const instructions = `<instructions>
+  <principles>
+  - Respond to intent, not just the question. When asked "how do I call generateText," also surface relevant configuration the caller probably doesn't know about \u2014 structured output options, response format controls, model-specific features. When asked "how do I parse JSON from a model response," recognize they're probably doing it wrong and suggest built-in structured output instead.
+  - Think at the workflow level. When the caller describes a multi-step process ("take user input, call an LLM, extract entities, save to database"), respond with the complete architectural approach: which actions to use, how to chain them, where to use batch execution, what error handling to add. Not just the signature for one action.
+  - Be opinionated about SDK usage. Make concrete recommendations about the right way to build things. "Use executeStepBatch here" is better than "you could optionally batch these." But stay grounded on model claims \u2014 only state facts from model metadata, not editorial judgments about quality.
+  - Match depth to the question. A simple "what params does generateImage take" gets a concise answer with a code example. A workflow question gets the full architectural response. Don't over-explain simple lookups, don't under-serve complex ones.
+  </principles>
+
+  <anti_patterns>
+  Flag these when the caller's question implies them:
+
+  - **Manual JSON parsing from LLM output** \u2014 if they're calling generateText and then parsing the response, they probably want structured output / response format controls instead of \`JSON.parse(content)\`.
+  - **Sequential calls that should be batched** \u2014 multiple independent action calls (generate image + text-to-speech + search) should use \`executeStepBatch()\`. Three round trips become one.
+  - **Building custom HTTP integrations when a connector exists** \u2014 if they're asking how to call the Slack API, Airtable API, HubSpot API, etc. via \`httpRequest\`, the answer is \`runFromConnectorRegistry\` with an existing OAuth connector. 850+ connector actions exist for this.
+  - **Missing MindStudioError handling** \u2014 the SDK has structured errors with \`code\`, \`status\`, \`details\`. Catching generic \`Error\` loses actionable information. Always include \`MindStudioError\` handling in code examples.
+  - **One-at-a-time db writes when batch exists** \u2014 N sequential \`update()\` or \`push()\` calls should be a single \`db.batch()\` call. One round trip instead of N.
+  - **Hardcoded model IDs without context** \u2014 model IDs can change. When writing code with a specific model, include a comment noting which model it is and why it was chosen, so the caller can swap it later.
+  </anti_patterns>
+
   <tools>
-  You have 3 tools for detailed lookups. Most questions can be answered from the reference above without tools.
+  You have 3 tools for detailed lookups. Most questions can be answered from the reference above without tools. Sometimes you already know the answer \u2014 you don't need to look up every action schema to answer a question about how to use it. Use tools when you need exact param types, model config options, or connector action details.
 
   - **getActionDetails(actionName)** \u2014 Full JSON schema for a specific action. Use when you need exact param types/enums to write correct code.
   - **listModels(type?, details?)** \u2014 Model catalog. By default returns compact summaries. With \`details: true\`, returns full model objects including the \`inputs\` array that defines config options (width, height, seed, etc.). Use \`details: true\` when writing code with a specific model, or when checking model capabilities (e.g. which models support source images). You can filter the full response yourself \u2014 one call with details is better than many individual lookups.
@@ -4288,15 +4314,14 @@ async function buildSystemPrompt(agent) {
   </tools>
 
   <response_format>
-  - Be terse. Lead with code \u2014 if the question implies code, the code block is the first thing in your response.
-  - Return complete, copy-paste-ready TypeScript code with correct model IDs, config options, and types.
+  - Lead with the right approach, then code. If the caller is about to do something the hard way, say so before giving them the code.
+  - Every response that involves code must include a complete, copy-paste-ready TypeScript example that handles the full use case \u2014 not just the one method call they asked about, but the surrounding pattern (error handling with MindStudioError, response destructuring, type annotations where helpful).
   - When writing code that uses a specific model, call listModels with details=true to get the model's config options and include them.
   - When building code examples, use getActionDetails to get the exact input schema first.
   - After the code block, optionally list config constraints (ranges, defaults) in a compact format.
   - For discovery questions ("what can I do?"), return a compact list from the reference docs.
   - Assume the caller already knows what the SDK is, how to install it, and how auth works.
-  - Only state facts from the data you have. Do not editorialize, recommend, or compare models/actions beyond what their metadata says. If the data does not say a model is "strong" or "best" at something, do not claim it is.
-  - Model tags in the summary are editorial labels, not technical specs. When answering questions about model capabilities (supported inputs, config options, dimensions, etc.), call listModels with details=true to check the \`inputs\` array \u2014 that is the source of truth. For example, a model supports start frame images if it has an input with type "imageUrl" or "imageUrlArray", not because its tags say "Source Image".
+  - Model tags in the summary are editorial labels, not technical specs. When answering questions about model capabilities (supported inputs, config options, dimensions, etc.), call listModels with details=true to check the \`inputs\` array \u2014 that is the source of truth.
   </response_format>
 </instructions>`;
   return `${identity}
@@ -4522,7 +4547,7 @@ async function startMcpServer(options) {
           capabilities: { tools: {} },
           serverInfo: {
             name: "mindstudio-agent",
-            version: "0.1.20"
+            version: "0.1.21"
           },
           instructions: 'Welcome to MindStudio \u2014 a platform with 200+ AI models, 850+ third-party integrations, and pre-built agents.\n\nGetting started:\n1. Call `ask` with any question about the SDK \u2014 it knows every action, model, and connector and returns working code with real model IDs and config options. Examples: ask("generate an image with FLUX"), ask("what models support vision?"), ask("how do I send a Slack message?").\n2. Call `changeName` to set your display name \u2014 use your name or whatever your user calls you. This is how you\'ll appear in MindStudio request logs.\n3. If you have a profile picture or icon, call `uploadFile` to upload it, then `changeProfilePicture` with the returned URL.\n4. For manual browsing, call `listActions` to discover all available actions.\n\nThen use the tools to generate text, images, video, audio, search the web, work with data sources, run agents, and more.\n\nImportant:\n- AI-powered actions (text generation, image generation, video, audio, etc.) cost money. Before running these, call `estimateActionCost` and confirm with the user before proceeding \u2014 unless they\'ve explicitly told you to go ahead.\n- Not all agents from `listAgents` are configured for API use. Do not try to run an agent just because it appears in the list \u2014 it will likely fail. Only run agents the user specifically asks you to run.'
         });
@@ -4991,6 +5016,7 @@ Account:
   change-name <name>                   Update your display name
   change-profile-picture <url>         Update your profile picture
   upload <filepath>                    Upload a file to the MindStudio CDN
+  update                               Update to the latest version
 
 OAuth integrations:
   list-connectors [<id> [<actionId>]]  Browse OAuth connector services
@@ -5456,7 +5482,7 @@ function isNewerVersion(current, latest) {
   return false;
 }
 async function checkForUpdate() {
-  const currentVersion = "0.1.20";
+  const currentVersion = "0.1.21";
   if (!currentVersion) return null;
   try {
     const { loadConfig: loadConfig2, saveConfig: saveConfig2 } = await Promise.resolve().then(() => (init_config(), config_exports));
@@ -5485,13 +5511,86 @@ async function checkForUpdate() {
   }
 }
 function printUpdateNotice(latestVersion) {
-  const currentVersion = "0.1.20";
+  const currentVersion = "0.1.21";
   process.stderr.write(
     `
   ${ansi2.cyanBright("Update available")} ${ansi2.gray(currentVersion + " \u2192")} ${ansi2.cyanBold(latestVersion)}
-  ${ansi2.gray("Run")} npm install -g @mindstudio-ai/agent ${ansi2.gray("to update")}
+  ${ansi2.gray("Run")} mindstudio update ${ansi2.gray("to update")}
+`
+  );
+}
+function isStandaloneBinary() {
+  const argv1 = process.argv[1] ?? "";
+  return !argv1.includes("node_modules");
+}
+async function cmdUpdate() {
+  const currentVersion = "0.1.21";
+  process.stderr.write(
+    `  ${ansi2.gray("Current version:")} ${currentVersion}
+`
+  );
+  process.stderr.write(`  ${ansi2.gray("Checking for updates...")}
+`);
+  let latestVersion;
+  try {
+    const res = await fetch(
+      "https://registry.npmjs.org/@mindstudio-ai/agent/latest",
+      { signal: AbortSignal.timeout(1e4) }
+    );
+    if (!res.ok) {
+      fatal("Failed to check for updates. Please try again later.");
+    }
+    const data = await res.json();
+    latestVersion = data.version ?? "";
+    if (!latestVersion) {
+      fatal("Failed to check for updates. Please try again later.");
+    }
+  } catch {
+    fatal(
+      "Failed to check for updates. Please check your internet connection."
+    );
+  }
+  if (!isNewerVersion(currentVersion, latestVersion)) {
+    process.stderr.write(
+      `  ${ansi2.greenBold("Already up to date!")} ${ansi2.gray("(" + currentVersion + ")")}
+`
+    );
+    return;
+  }
+  process.stderr.write(
+    `  ${ansi2.cyanBright("Updating")} ${ansi2.gray(currentVersion + " \u2192")} ${ansi2.cyanBold(latestVersion)}
 `
   );
+  if (isStandaloneBinary()) {
+    const platform = process.platform;
+    try {
+      if (platform === "win32") {
+        execSync(
+          'powershell -Command "irm https://msagent.ai/install.ps1 | iex"',
+          { stdio: "inherit" }
+        );
+      } else {
+        execSync("curl -fsSL https://msagent.ai/install.sh | bash", {
+          stdio: "inherit"
+        });
+      }
+      process.stderr.write(
+        `
+  ${ansi2.greenBold("Updated to " + latestVersion)}
+`
+      );
+    } catch {
+      fatal("Update failed. Try running the install command manually.");
+    }
+  } else {
+    process.stderr.write(
+      `
+  ${ansi2.gray("Run the following command to update:")}
+
+  npm install -g @mindstudio-ai/agent@latest
+`
+    );
+  }
 }
 var LOGO = `       .=+-.     :++.
       *@@@@@+  :%@@@@%:
@@ -5560,7 +5659,7 @@ async function cmdLogin(options) {
   process.stderr.write("\n");
   printLogo();
   process.stderr.write("\n");
-  const ver = "0.1.20";
+  const ver = "0.1.21";
   process.stderr.write(
     `  ${ansi2.bold("MindStudio Agent")} ${ver ? " " + ansi2.gray("v" + ver) : ""}
 `
@@ -5869,11 +5968,11 @@ async function main() {
     process.exit(1);
   }
   const command = positionals[0];
-  const updatePromise = command !== "mcp" && command !== "login" ? checkForUpdate() : Promise.resolve(null);
+  const updatePromise = command !== "mcp" && command !== "login" && command !== "update" ? checkForUpdate() : Promise.resolve(null);
   try {
     if (command === "version" || command === "-v") {
       process.stdout.write(
-        "0.1.20\n"
+        "0.1.21\n"
       );
       return;
     }
@@ -5894,6 +5993,10 @@ async function main() {
       });
       return;
     }
+    if (command === "update") {
+      await cmdUpdate();
+      return;
+    }
     if (command === "ask") {
       let question = positionals.slice(1).join(" ");
       if (!question && !process.stdin.isTTY) {