@mindstudio-ai/agent 0.1.95 → 0.1.97

package/dist/cli.js

@@ -3546,9 +3546,13 @@ var init_source = __esm({
        * or a regression check on top of it. There is no seed to set. Two things do
        * legitimately move the results: adding or removing documents, and changing
        * the corpus configuration — both of which you control.
+       *
+       * Alongside `results` and `latencyMs` comes {@link SearchRan} — what the
+       * search actually did, which is the first thing to check when results don't
+       * look like the options you passed.
        */
       async search(query, options) {
-        const { results, latencyMs } = await this._call("search", {
+        const { results, mode, latencyMs } = await this._call("search", {
           slug: this._slug,
           query,
           ...options?.topK !== void 0 ? { topK: options.topK } : {},
@@ -3562,7 +3566,7 @@ var init_source = __esm({
           ...options?.explain !== void 0 ? { explain: options.explain } : {},
           ...options?.expand !== void 0 ? { expand: options.expand } : {}
         });
-        return { results: results ?? [], latencyMs: latencyMs ?? 0 };
+        return { results: results ?? [], mode, latencyMs: latencyMs ?? 0 };
       }
       /**
        * What is in the corpus, and how it was built.
@@ -7333,7 +7337,7 @@ async function startMcpServer(options) {
           capabilities: { tools: {} },
           serverInfo: {
             name: "mindstudio-agent",
-            version: "0.1.95"
+            version: "0.1.97"
           },
           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, pass its public image URL to `changeProfilePicture`.\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.'
         });
@@ -8318,7 +8322,7 @@ function isNewerVersion(current, latest) {
   return false;
 }
 async function checkForUpdate() {
-  const currentVersion = "0.1.95";
+  const currentVersion = "0.1.97";
   if (!currentVersion) return null;
   try {
     const { loadConfig: loadConfig2, saveConfig: saveConfig2 } = await Promise.resolve().then(() => (init_config(), config_exports));
@@ -8347,7 +8351,7 @@ async function checkForUpdate() {
   }
 }
 function printUpdateNotice(latestVersion) {
-  const currentVersion = "0.1.95";
+  const currentVersion = "0.1.97";
   process.stderr.write(
     `
   ${ansi2.cyanBright("Update available")} ${ansi2.gray(currentVersion + " \u2192")} ${ansi2.cyanBold(latestVersion)}
@@ -8360,7 +8364,7 @@ function isStandaloneBinary() {
   return !argv1.includes("node_modules");
 }
 async function cmdUpdate() {
-  const currentVersion = "0.1.95";
+  const currentVersion = "0.1.97";
   process.stderr.write(
     `  ${ansi2.gray("Current version:")} ${currentVersion}
 `
@@ -8495,7 +8499,7 @@ async function cmdLogin(options) {
   process.stderr.write("\n");
   printLogo();
   process.stderr.write("\n");
-  const ver = "0.1.95";
+  const ver = "0.1.97";
   process.stderr.write(
     `  ${ansi2.bold("MindStudio Agent")} ${ver ? " " + ansi2.gray("v" + ver) : ""}
 `
@@ -8822,7 +8826,7 @@ async function main() {
   try {
     if (command === "version" || command === "-v") {
       process.stdout.write(
-        "0.1.95\n"
+        "0.1.97\n"
       );
       return;
     }

package/dist/index.d.ts

@@ -1672,15 +1672,35 @@ interface SearchHit {
         after: string[];
     };
     /**
-     * Only when `highlight` was requested: where query terms land in `text`, as
-     * `text.slice(start, end)` ranges. Keyword-based — a hit that matched
-     * semantically may report an empty array, which is itself informative.
+     * Only when `highlight` was requested: where the query's most distinctive
+     * terms land in `text`, as `text.slice(start, end)` ranges, each carrying the
+     * `token` it matched so you can colour or group by term.
+     *
+     * NOT every query term — see {@link SearchOptions.highlight}. Keyword-based,
+     * so a hit that matched semantically may report an empty array, which is
+     * itself informative.
      */
     matches?: {
         start: number;
         end: number;
+        token: string;
     }[];
 }
+/**
+ * What a search actually ran — as opposed to what was asked for.
+ *
+ * Worth checking when a result surprises you: an omitted `mode` falls back to
+ * the corpus's own configuration, and `reranked` is false when reranking was
+ * skipped or failed open. Absent only when the data source doesn't exist yet,
+ * in which case nothing ran at all.
+ */
+interface SearchRan {
+    search: SearchMode;
+    hybrid: boolean;
+    reranked: boolean;
+    /** Which build served the query. Changes when a re-vectorization is promoted. */
+    pipelineVersion: number;
+}
 /**
  * Per-query overrides.
  *
@@ -1717,8 +1737,16 @@ interface SearchOptions {
      */
     maxPerDocument?: number;
     /**
-     * Return `matches` on each hit: offsets of query terms within its text, for
-     * rendering highlights.
+     * Return {@link SearchHit.matches} on each hit: where query terms land in its
+     * text, for rendering highlights.
+     *
+     * Only the query's **distinctive** terms are marked. English function words —
+     * `the`, `for`, `is`, `of` — are never marked, and when a passage holds more
+     * matches than it can usefully show, the rarest terms win the space. So
+     * `what is the policy for parental leave` marks `policy`, `parental` and
+     * `leave`, and nothing else. Without that a natural-language query lights up
+     * most of the passage and you would need your own stopword list to render
+     * anything. Words you filtered on (`contains`, `phrase`) are always marked.
      */
     highlight?: boolean;
     /**
@@ -1868,9 +1896,14 @@ declare class DataSource {
      * or a regression check on top of it. There is no seed to set. Two things do
      * legitimately move the results: adding or removing documents, and changing
      * the corpus configuration — both of which you control.
+     *
+     * Alongside `results` and `latencyMs` comes {@link SearchRan} — what the
+     * search actually did, which is the first thing to check when results don't
+     * look like the options you passed.
      */
     search(query: string, options?: SearchOptions): Promise<{
         results: SearchHit[];
+        mode?: SearchRan;
         latencyMs: number;
     }>;
     /**
@@ -9676,7 +9709,14 @@ declare class MindStudioError extends Error {
  * Channel-discriminated so future surfaces extend without breaking.
  */
 interface SessionContext {
-    channel: 'voice' | 'agent';
+    /**
+     * Which surface invoked this method: `voice`/`agent` for conversational
+     * tool calls (which carry their session/thread ids below), `web` for a
+     * browser interface-session method call, `api` for an app-key or
+     * platform-key call. `web`/`api` carry only `visitorId`. Absent entirely
+     * on older platform versions.
+     */
+    channel: 'voice' | 'agent' | 'web' | 'api';
     /** Voice-session id — matches the browser voice client's `session.sessionId`. */
     voiceSessionId?: string;
     /** Agent-chat thread id. */

package/dist/index.js

@@ -2149,9 +2149,13 @@ var DataSource = class {
    * or a regression check on top of it. There is no seed to set. Two things do
    * legitimately move the results: adding or removing documents, and changing
    * the corpus configuration — both of which you control.
+   *
+   * Alongside `results` and `latencyMs` comes {@link SearchRan} — what the
+   * search actually did, which is the first thing to check when results don't
+   * look like the options you passed.
    */
   async search(query, options) {
-    const { results, latencyMs } = await this._call("search", {
+    const { results, mode, latencyMs } = await this._call("search", {
       slug: this._slug,
       query,
       ...options?.topK !== void 0 ? { topK: options.topK } : {},
@@ -2165,7 +2169,7 @@ var DataSource = class {
       ...options?.explain !== void 0 ? { explain: options.explain } : {},
       ...options?.expand !== void 0 ? { expand: options.expand } : {}
     });
-    return { results: results ?? [], latencyMs: latencyMs ?? 0 };
+    return { results: results ?? [], mode, latencyMs: latencyMs ?? 0 };
   }
   /**
    * What is in the corpus, and how it was built.