@memnexus-ai/sdk 1.75.5 → 1.76.0

package/dist/index.cjs

@@ -1396,6 +1396,27 @@ var Memories = class {
    * matching into a single call. Eliminates the 5+ round-trip pattern agents
    * use today.
    * 
+   * **Project scoping (optional).** Send `scope` as comma-separated
+   * `key:value` pairs (allowed keys: `product`, `service`, `team`, `role`) —
+   * the same format the list and search endpoints accept — to restrict the
+   * briefing to one project. All pairs must match (AND), so each extra key
+   * can only shrink the result set; send the fewest keys that identify the
+   * project (`product:<project>` is the recommended default). An unknown
+   * key, or a `scope` string that yields no valid `key:value` pair at all,
+   * returns 400 — a scope request that cannot be honoured is never
+   * silently downgraded to an unscoped briefing.
+   * 
+   * When `scope` is set, memories that carry no `codeContext` at all are
+   * excluded by default: a scoped request returns scoped content only. Send
+   * `includeUnscoped: true` to also include unlabeled memories. Without
+   * `scope` the flag is inert — accepted, no filter runs, and neither field
+   * is echoed in `meta`. Omitting `scope` reproduces today's behavior exactly.
+   * 
+   * Two sections cannot be scope-filtered and are named in
+   * `meta.unfilteredSections` on any scoped request rather than being served
+   * as if they had been filtered: `relatedPatterns` (Pattern nodes carry no
+   * `codeContext`) and `commitContext` (an account-wide adoption count).
+   * 
    * @param body — Request body
    */
   async buildContext(body) {

package/dist/index.d.cts

@@ -1515,6 +1515,10 @@ interface BuildContextRequest {
     files?: string[];
     /** How far back to look for recent activity (hours, default 24) */
     recentHours?: number;
+    /** Comma-separated codeContext key:value pairs to filter by. Allowed keys: product, service, team, role. All pairs must match (AND), so each extra key can only shrink the result set — a key your memories do not consistently carry will silently empty the brief. Send the fewest keys that identify the project; product:<project> alone is the recommended default. An unknown key, or a string that yields no valid key:value pair at all, returns 400 rather than an unscoped brief. */
+    scope?: string;
+    /** When scope is set, whether to also return memories that carry no codeContext at all. Defaults to false when scope is set — a scoped request returns scoped content only. Send true to also include memories that carry no codeContext. Inert when scope is absent. */
+    includeUnscoped?: boolean;
 }
 /** Most relevant active conversation, or null if none found */
 interface BuildContextActiveWork {
@@ -1574,6 +1578,12 @@ interface BuildContextMeta {
     contextTerms: string[];
     /** Hours window used for recent activity */
     recentHours: number;
+    /** The parsed codeContext scope the request was filtered by. Present only when the request sent a scope. */
+    scope?: Record<string, unknown>;
+    /** The RESOLVED includeUnscoped value the request ran with — false when the caller sent scope and omitted the field. Present only when the request sent a scope; without scope the flag is inert and is not echoed. */
+    includeUnscoped?: boolean;
+    /** Sections the scope filter did not constrain, so a caller never has to assume a section was filtered when it was not. relatedPatterns cannot be scoped (Pattern nodes carry no codeContext and no path back to a source memory); commitContext is an account-wide adoption count by design. Present only when the request sent a scope. */
+    unfilteredSections?: string[];
     /** Sections whose backing query exceeded the per-branch timeout and were returned empty. Present only when at least one branch timed out, so an empty section can otherwise be read as 'no data'. */
     timedOutSections?: string[];
 }
@@ -2865,12 +2875,35 @@ declare class Memories {
      * matching into a single call. Eliminates the 5+ round-trip pattern agents
      * use today.
      *
+     * **Project scoping (optional).** Send `scope` as comma-separated
+     * `key:value` pairs (allowed keys: `product`, `service`, `team`, `role`) —
+     * the same format the list and search endpoints accept — to restrict the
+     * briefing to one project. All pairs must match (AND), so each extra key
+     * can only shrink the result set; send the fewest keys that identify the
+     * project (`product:<project>` is the recommended default). An unknown
+     * key, or a `scope` string that yields no valid `key:value` pair at all,
+     * returns 400 — a scope request that cannot be honoured is never
+     * silently downgraded to an unscoped briefing.
+     *
+     * When `scope` is set, memories that carry no `codeContext` at all are
+     * excluded by default: a scoped request returns scoped content only. Send
+     * `includeUnscoped: true` to also include unlabeled memories. Without
+     * `scope` the flag is inert — accepted, no filter runs, and neither field
+     * is echoed in `meta`. Omitting `scope` reproduces today's behavior exactly.
+     *
+     * Two sections cannot be scope-filtered and are named in
+     * `meta.unfilteredSections` on any scoped request rather than being served
+     * as if they had been filtered: `relatedPatterns` (Pattern nodes carry no
+     * `codeContext`) and `commitContext` (an account-wide adoption count).
+     *
      * @param body — Request body
      */
     buildContext(body: {
         context: string;
         files?: string[];
         recentHours?: number;
+        scope?: string;
+        includeUnscoped?: boolean;
     }): Promise<HttpResponse<{
         activeWork: BuildContextActiveWork;
         relevantFacts: BuildContextFact[];

package/dist/index.d.ts

@@ -1515,6 +1515,10 @@ interface BuildContextRequest {
     files?: string[];
     /** How far back to look for recent activity (hours, default 24) */
     recentHours?: number;
+    /** Comma-separated codeContext key:value pairs to filter by. Allowed keys: product, service, team, role. All pairs must match (AND), so each extra key can only shrink the result set — a key your memories do not consistently carry will silently empty the brief. Send the fewest keys that identify the project; product:<project> alone is the recommended default. An unknown key, or a string that yields no valid key:value pair at all, returns 400 rather than an unscoped brief. */
+    scope?: string;
+    /** When scope is set, whether to also return memories that carry no codeContext at all. Defaults to false when scope is set — a scoped request returns scoped content only. Send true to also include memories that carry no codeContext. Inert when scope is absent. */
+    includeUnscoped?: boolean;
 }
 /** Most relevant active conversation, or null if none found */
 interface BuildContextActiveWork {
@@ -1574,6 +1578,12 @@ interface BuildContextMeta {
     contextTerms: string[];
     /** Hours window used for recent activity */
     recentHours: number;
+    /** The parsed codeContext scope the request was filtered by. Present only when the request sent a scope. */
+    scope?: Record<string, unknown>;
+    /** The RESOLVED includeUnscoped value the request ran with — false when the caller sent scope and omitted the field. Present only when the request sent a scope; without scope the flag is inert and is not echoed. */
+    includeUnscoped?: boolean;
+    /** Sections the scope filter did not constrain, so a caller never has to assume a section was filtered when it was not. relatedPatterns cannot be scoped (Pattern nodes carry no codeContext and no path back to a source memory); commitContext is an account-wide adoption count by design. Present only when the request sent a scope. */
+    unfilteredSections?: string[];
     /** Sections whose backing query exceeded the per-branch timeout and were returned empty. Present only when at least one branch timed out, so an empty section can otherwise be read as 'no data'. */
     timedOutSections?: string[];
 }
@@ -2865,12 +2875,35 @@ declare class Memories {
      * matching into a single call. Eliminates the 5+ round-trip pattern agents
      * use today.
      *
+     * **Project scoping (optional).** Send `scope` as comma-separated
+     * `key:value` pairs (allowed keys: `product`, `service`, `team`, `role`) —
+     * the same format the list and search endpoints accept — to restrict the
+     * briefing to one project. All pairs must match (AND), so each extra key
+     * can only shrink the result set; send the fewest keys that identify the
+     * project (`product:<project>` is the recommended default). An unknown
+     * key, or a `scope` string that yields no valid `key:value` pair at all,
+     * returns 400 — a scope request that cannot be honoured is never
+     * silently downgraded to an unscoped briefing.
+     *
+     * When `scope` is set, memories that carry no `codeContext` at all are
+     * excluded by default: a scoped request returns scoped content only. Send
+     * `includeUnscoped: true` to also include unlabeled memories. Without
+     * `scope` the flag is inert — accepted, no filter runs, and neither field
+     * is echoed in `meta`. Omitting `scope` reproduces today's behavior exactly.
+     *
+     * Two sections cannot be scope-filtered and are named in
+     * `meta.unfilteredSections` on any scoped request rather than being served
+     * as if they had been filtered: `relatedPatterns` (Pattern nodes carry no
+     * `codeContext`) and `commitContext` (an account-wide adoption count).
+     *
      * @param body — Request body
      */
     buildContext(body: {
         context: string;
         files?: string[];
         recentHours?: number;
+        scope?: string;
+        includeUnscoped?: boolean;
     }): Promise<HttpResponse<{
         activeWork: BuildContextActiveWork;
         relevantFacts: BuildContextFact[];

package/dist/index.js

@@ -1369,6 +1369,27 @@ var Memories = class {
    * matching into a single call. Eliminates the 5+ round-trip pattern agents
    * use today.
    * 
+   * **Project scoping (optional).** Send `scope` as comma-separated
+   * `key:value` pairs (allowed keys: `product`, `service`, `team`, `role`) —
+   * the same format the list and search endpoints accept — to restrict the
+   * briefing to one project. All pairs must match (AND), so each extra key
+   * can only shrink the result set; send the fewest keys that identify the
+   * project (`product:<project>` is the recommended default). An unknown
+   * key, or a `scope` string that yields no valid `key:value` pair at all,
+   * returns 400 — a scope request that cannot be honoured is never
+   * silently downgraded to an unscoped briefing.
+   * 
+   * When `scope` is set, memories that carry no `codeContext` at all are
+   * excluded by default: a scoped request returns scoped content only. Send
+   * `includeUnscoped: true` to also include unlabeled memories. Without
+   * `scope` the flag is inert — accepted, no filter runs, and neither field
+   * is echoed in `meta`. Omitting `scope` reproduces today's behavior exactly.
+   * 
+   * Two sections cannot be scope-filtered and are named in
+   * `meta.unfilteredSections` on any scoped request rather than being served
+   * as if they had been filtered: `relatedPatterns` (Pattern nodes carry no
+   * `codeContext`) and `commitContext` (an account-wide adoption count).
+   * 
    * @param body — Request body
    */
   async buildContext(body) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@memnexus-ai/sdk",
-  "version": "1.75.5",
+  "version": "1.76.0",
   "description": "Official Node.js SDK for the MemNexus API",
   "license": "Proprietary",
   "type": "module",